git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Langhoff <martin.langhoff@gmail.com>
To: Marco Costalba <mcostalba@yahoo.it>
Cc: Daniel Barkalow <barkalow@iabervon.org>, git@vger.kernel.org
Subject: Re: [RFC] Patches exchange is bad?
Date: Wed, 17 Aug 2005 21:07:19 +1200	[thread overview]
Message-ID: <46a038f90508170207578b1c0@mail.gmail.com> (raw)
In-Reply-To: <20050817082709.28135.qmail@web26301.mail.ukl.yahoo.com>

On 8/17/05, Marco Costalba <mcostalba@yahoo.it> wrote:
> Of course I can feed proper subject and description to git-commit but I would like
> to find something less intrusive

I don't know if it helps, but I think that StGIT is what you are
looking for, not only because you have more tools to deal with
patches, but also because patches that are in the 'stack' are actually
really malleable. You can edit and reedit the patch w its commit msg
and all, commit it to the stack, and reedit it again later. It only
becomes immutable when you commit to the underlying git repo.

cheers,


martin

  reply	other threads:[~2005-08-17  9:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-17  8:27 [RFC] Patches exchange is bad? Marco Costalba
2005-08-17  9:07 ` Martin Langhoff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-08-18 13:34 Marco Costalba
2005-08-18 13:41 ` Catalin Marinas
2005-08-18 10:00 Marco Costalba
2005-08-18 11:16 ` Catalin Marinas
2005-08-17 18:03 Marco Costalba
2005-08-17 17:35 Marco Costalba
2005-08-17 21:27 ` Catalin Marinas
2005-08-17 21:37   ` Johannes Schindelin
2005-08-18 10:27     ` Catalin Marinas
2005-08-16 22:09 Marco Costalba
2005-08-16 22:45 ` Daniel Barkalow
2005-08-16 21:47 Marco Costalba
2005-08-16 20:01 Marco Costalba
2005-08-16 20:39 ` Johannes Schindelin
2005-08-16 21:02 ` Junio C Hamano
2005-08-16 21:31 ` Martin Langhoff
2005-08-17 17:12 ` 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=46a038f90508170207578b1c0@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=barkalow@iabervon.org \
    --cc=git@vger.kernel.org \
    --cc=mcostalba@yahoo.it \
    /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).