From: Yann Dirson <ydirson@altern.org>
To: "Catalin Marinas" <catalin.marinas@gmail.com>,
"Karl Hasselström" <kha@treskal.com>
Cc: GIT list <git@vger.kernel.org>
Subject: stgit restrictions on patch names
Date: Thu, 25 Oct 2007 21:48:08 +0200 [thread overview]
Message-ID: <20071025194808.GV26436@nan92-1-81-57-214-146.fbx.proxad.net> (raw)
Looks like stgit is now more picky on patch names than in used to be:
$ stg branch --clone v2.0.6-debian
Checking for changes in the working directory ... done
Cloning current branch to "v2.0.6-debian" ...
No log for 01_springelectrical
stg branch: Invalid patch name: "10_g++4.0_build_failures"
$
=> the result of the cloning operation is a partial clone. Do we want to:
- implement a mechanism for checking beforehand that the operation
will not fail ? Seems awkward to duplicate checks already found
elsewhere.
- wait for proper transactions so we can rollback on error ?
- on clone error, delete the newly-created stack ? I'd vote for this
one, until the previous one gets done.
=> is there any particular reason why we would refuse "+" ?
next reply other threads:[~2007-10-25 19:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 19:48 Yann Dirson [this message]
2007-10-26 7:29 ` stgit restrictions on patch names Karl Hasselström
2007-10-29 16:14 ` 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
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=20071025194808.GV26436@nan92-1-81-57-214-146.fbx.proxad.net \
--to=ydirson@altern.org \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=kha@treskal.com \
/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).