From: Chuck Lever <cel@citi.umich.edu>
To: catalin.marinas@gmail.com
Cc: git@vger.kernel.org
Subject: [PATCH 0/2] allow patches called "applied", "current", and so on
Date: Sun, 29 Jan 2006 13:10:04 -0500 [thread overview]
Message-ID: <20060129181004.1919.92166.stgit@dexter.citi.umich.edu> (raw)
The following patches create a separate directory for patches so that patch
names like "applied" don't collide with the patch series control files.
A new option on the "stg branch" command allows users to convert between the
old-style (all in the same series directory) and the new-style (patches in a
separate directory). "stg" should be good at detecting which type of
repository is in use and adapting to it, so this change should be entirely
invisible on legacy repositories.
-- Chuck Lever
--
corporate: <cel at netapp dot com>
personal: <chucklever at bigfoot dot com>
next reply other threads:[~2006-01-29 18:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-29 18:10 Chuck Lever [this message]
2006-01-29 18:13 ` [PATCH 1/2] Use a separate directory for patches under each branch subdir Chuck Lever
2006-01-29 18:14 ` [PATCH 2/2] Add an option to "stg branch" to convert the internal format Chuck Lever
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060129181004.1919.92166.stgit@dexter.citi.umich.edu \
--to=cel@citi.umich.edu \
--cc=catalin.marinas@gmail.com \
--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.
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 NNTP newsgroup(s).