From: "Marco Costalba" <mcostalba@gmail.com>
To: "Jan Hudec" <bulb@ucw.cz>
Cc: git@vger.kernel.org
Subject: Re: [Qgit PATCH] Add ability to commit --amend
Date: Fri, 21 Mar 2008 03:11:50 +0100 [thread overview]
Message-ID: <e5bfff550803201911xf2250d2w2064a23a84b2480f@mail.gmail.com> (raw)
In-Reply-To: <20080320193957.GA12119@efreet.light.src>
On Thu, Mar 20, 2008 at 8:39 PM, Jan Hudec <bulb@ucw.cz> wrote:
>
> It seems to work for me. I didn't try any particularly nasty cases, but on
> the other hand I didn't change the commit logic itself, so it should not have
> effect on this. Please review and apply if it looks OK.
>
Patch reviewed (It seems very good) applied and pushed.
>
> So what I'd like to look into now is introducing two classes, one for plain
> git core branches and one for stgit repositories. They will create the
> actions that depend on repository type (so they would no longer be designed,
> but QActions are quite simple, so I don't think it's critical). They will
> share code as appropriate via inheritance or delegation to current Git class.
> This should make the code a little more modular and make it possible if some
> day someone decides to add support for guilt or other git extension.
>
This does not seem an easy task (especially for the git part), of
course you are more then welcomed ;-)
>
> PS: Is this the right way to submit QGit patches, or should I be using some
> other channel (like sf.net patch tracker or something)?
>
Yes it is (if people on the list does not complain), I don't expect a
lot of bandwidth used for qgit patches and we (possible contributors)
commonly read git list, not sourceforge one.
Thanks
Marco
prev parent reply other threads:[~2008-03-21 2:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 19:39 [Qgit PATCH] Add ability to commit --amend Jan Hudec
2008-03-21 2:11 ` Marco Costalba [this message]
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=e5bfff550803201911xf2250d2w2064a23a84b2480f@mail.gmail.com \
--to=mcostalba@gmail.com \
--cc=bulb@ucw.cz \
--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).