git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Thomas Ackermann <th.acker@arcor.de>
To: th.acker@arcor.de, git@vger.kernel.org
Subject: [PATCH 1/3] Move CodingGuidelines to ./technical/coding-guidelines.txt and SubmittingPatches to ./technical/submitting-patches.txt
Date: Sun, 30 Dec 2012 11:31:54 +0100 (CET)	[thread overview]
Message-ID: <1979101508.1364078.1356863514997.JavaMail.ngmail@webmail19.arcor-online.net> (raw)
In-Reply-To: <1023165134.213650.1356863340563.JavaMail.ngmail@webmail06.arcor-online.net>


Signed-off-by: Thomas Ackermann <th.acker@arcor.de>
---
 Documentation/{CodingGuidelines => technical/coding-guidelines.txt}   | 0
 Documentation/{SubmittingPatches => technical/submitting-patches.txt} | 0
 2 files changed, 0 insertions(+), 0 deletions(-)
 rename Documentation/{CodingGuidelines => technical/coding-guidelines.txt} (100%)
 rename Documentation/{SubmittingPatches => technical/submitting-patches.txt} (100%)

diff --git a/Documentation/CodingGuidelines b/Documentation/technical/coding-guidelines.txt
similarity index 100%
rename from Documentation/CodingGuidelines
rename to Documentation/technical/coding-guidelines.txt
diff --git a/Documentation/SubmittingPatches b/Documentation/technical/submitting-patches.txt
similarity index 100%
rename from Documentation/SubmittingPatches
rename to Documentation/technical/submitting-patches.txt
-- 
1.8.0.msysgit.0


---
Thomas

  reply	other threads:[~2012-12-30 10:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-30 10:29 [PATCH 0/3] Move CodingGuidelines and SubmittingPatches to ./Documentation/technical Thomas Ackermann
2012-12-30 10:31 ` Thomas Ackermann [this message]
2012-12-30 10:33 ` [PATCH 2/3] Add coding-guidelines.txt and submitting-patches.txt to ./Documentation/Makefile Thomas Ackermann
2012-12-30 10:35 ` [PATCH 3/3] Convert coding-guidelines.txt and submitting-patches.txt to asciidoc Thomas Ackermann
2012-12-30 11:52 ` [PATCH 0/3] Move CodingGuidelines and SubmittingPatches to ./Documentation/technical Ramkumar Ramachandra

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1979101508.1364078.1356863514997.JavaMail.ngmail@webmail19.arcor-online.net \
    --to=th.acker@arcor.de \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).