From: Chuck Lever <cel@citi.umich.edu>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 7/7] Use a separate directory for patches under each branch subdir
Date: Wed, 30 Nov 2005 17:28:39 -0500 [thread overview]
Message-ID: <438E2797.2020205@citi.umich.edu> (raw)
In-Reply-To: <b0943d9e0511301423h2885d442r@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 718 bytes --]
Catalin Marinas wrote:
> On 29/11/05, Chuck Lever <cel@netapp.com> wrote:
>
>>Currently you can't specify a patch name that matches the name of one of
>>the stgit special files under .git/patches/<branch-name>. Let's use a
>>new subdirectory under .git/patches/<branch-name> to contain just the
>>patch directories to remove this limitation.
>
>
> This patch doesn't fix the already created branches. It would be
> useful to upgrade the branch structure automatically if the patches
> directory is not found.
the reason i didn't do that is because i wanted to allow older versions
of StGIT to continue to work on existing repositories.
what if i added a migration tool to allow a user to switch back and forth?
[-- Attachment #2: cel.vcf --]
[-- Type: text/x-vcard, Size: 439 bytes --]
begin:vcard
fn:Chuck Lever
n:Lever;Charles
org:Network Appliance, Incorporated;Linux NFS Client Development
adr:535 West William Street, Suite 3100;;Center for Information Technology Integration;Ann Arbor;MI;48103-4943;USA
email;internet:cel@citi.umich.edu
title:Member of Technical Staff
tel;work:+1 734 763 4415
tel;fax:+1 734 763 4434
tel;home:+1 734 668 1089
x-mozilla-html:FALSE
url:http://www.monkey.org/~cel/
version:2.1
end:vcard
next prev parent reply other threads:[~2005-11-30 22:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-29 22:05 [PATCH 0/7] Chuck Lever
2005-11-29 22:09 ` [PATCH 1/7] Make "stg export" save the base commit in the output directory Chuck Lever
2005-11-30 21:53 ` Catalin Marinas
2005-11-29 22:09 ` [PATCH 2/7] Use git-rev-parse to find the local GIT repository Chuck Lever
2005-11-29 22:09 ` [PATCH 3/7] Align branch descriptions in output of "stg branch -l" Chuck Lever
2005-11-29 22:09 ` [PATCH 4/7] "stg series" option to show patch summary descriptions Chuck Lever
2005-11-29 22:09 ` [PATCH 5/7] Add facility to print short list of patches around 'top' Chuck Lever
2005-11-29 22:09 ` [PATCH 6/7] Add a "--clone" option to "stg branch" Chuck Lever
2005-12-01 21:05 ` Catalin Marinas
2005-12-01 21:47 ` Chuck Lever
2005-11-29 22:09 ` [PATCH 7/7] Use a separate directory for patches under each branch subdir Chuck Lever
2005-11-30 22:23 ` Catalin Marinas
2005-11-30 22:28 ` Chuck Lever [this message]
2005-11-30 22:32 ` Catalin Marinas
2005-12-01 2:53 ` Chuck Lever
2005-11-30 22:27 ` [PATCH 0/7] Catalin Marinas
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=438E2797.2020205@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).