From: "Catalin Marinas" <catalin.marinas@gmail.com>
To: "Karl Hasselström" <kha@treskal.com>
Cc: git@vger.kernel.org
Subject: Re: [StGIT PATCH 3/4] Convert git_id() to the new id format
Date: Sun, 13 Jul 2008 12:20:25 +0100 [thread overview]
Message-ID: <b0943d9e0807130420v37e36f30sef8b7745fa55b688@mail.gmail.com> (raw)
In-Reply-To: <20080622154854.GC4468@diana.vm.bytemark.co.uk>
2008/6/22 Karl Hasselström <kha@treskal.com>:
> On 2008-06-19 22:42:22 +0100, Catalin Marinas wrote:
>
>> The patch rewrites git_id() to use the new id format and coverts the
>> commands using this function. The git_id() will be removed once all
>> the commands are converted to the new infrastructure where
>> git_commit() will be used instead.
[...[
>> if not rev:
>> + # backwards compatibility
>> return None
>
> Could you expand this comment a bit? It's not enough of a clue for me.
> :-/
I removed it, the diff command used to pass None as rev2 if the user
only passed one boundary of the range. I fixed diff and removed the
above.
>> -def git_commit(name, repository, branch = None):
>> +def git_commit(name, repository, branch_name = None):
>
> Very nice parameter rename here, now that we have Branch objects (and
> use a crappy language with no type system).
It has a type system but no compile-time checking (I'm more in favour
of static typing but no time to rewrite stgit :-)).
>> - (refpatchname, refbranchname, refpatchid) = parse_rev(patchname)
>> - if refpatchname and not refpatchid and \
>> - (not refpatchid or refpatchid == 'top'):
>> - # FIXME: should also support picking //top.old
>> + refbranchname, refpatchname = parse_rev(patchname)
>> + if refpatchname:
>
> The corresponding TODO comment now would be that pick should be able
> to pick patches from the past, from the stack log.
How would the syntax look like?
--
Catalin
next prev parent reply other threads:[~2008-07-13 11:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 21:41 [StGIT PATCH 0/4] Proposed patches Catalin Marinas
2008-06-19 21:42 ` [StGIT PATCH 1/4] Allow e-mails to be sent with the Unix sendmail tool Catalin Marinas
2008-06-22 15:10 ` Karl Hasselström
2008-06-29 21:55 ` Catalin Marinas
2008-06-19 21:42 ` [StGIT PATCH 2/4] Implement a new patch identification scheme and id command Catalin Marinas
2008-06-22 15:27 ` Karl Hasselström
2008-06-19 21:42 ` [StGIT PATCH 3/4] Convert git_id() to the new id format Catalin Marinas
2008-06-22 15:48 ` Karl Hasselström
2008-07-13 11:20 ` Catalin Marinas [this message]
2008-07-14 6:44 ` Karl Hasselström
2008-06-19 21:42 ` [StGIT PATCH 4/4] Remove the applied/unapplied commands Catalin Marinas
2008-06-22 16:13 ` Karl Hasselström
2008-07-13 11:31 ` 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=b0943d9e0807130420v37e36f30sef8b7745fa55b688@mail.gmail.com \
--to=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.
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).