git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Clark Williams <clark.williams@gmail.com>
To: git@vger.kernel.org
Subject: StGit question
Date: Thu, 11 Sep 2008 12:04:06 -0500	[thread overview]
Message-ID: <48C94F86.6080707@gmail.com> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Are there any guidelines or best-practices for sharing StGit trees?

I'm working with the Linux -rt patchset and I need to be able to share my tree with
other people. What I'd *like* to do is push git tree's up to a git server, let other
people fetch them and have them be able to 'stg uncommit' to get back to my stack
state. The problem is that when someone uncommits, you lose the patch names.  If
you're trying to create an RPM out of a stack, this causes problems :).

Is there something I can do or something that we can do to StGit to make it possible
for an 'uncommit' to restore the original patch name? It looks like I could modify
the commit message, so that the first line is the patch name, but that's not very
nice for people scanning commits.

Or am I missing something completely trivial that will make my life easier?

Thanks,
Clark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkjJT4UACgkQqA4JVb61b9d1tgCfeVNG1BkaZ9czZpeHrFumU+xW
3/kAnj307N0Wx5nLSmtIPr5d+UetAxEG
=uol3
-----END PGP SIGNATURE-----

             reply	other threads:[~2008-09-11 17:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-11 17:04 Clark Williams [this message]
2008-09-12  7:51 ` StGit question Karl Hasselström
2008-09-12 12:41   ` Clark Williams
2008-09-12 15:40     ` Karl Hasselström
2008-09-12 22:15     ` Catalin Marinas
2008-09-12 22:18       ` 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=48C94F86.6080707@gmail.com \
    --to=clark.williams@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).