StGit question
-----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-----
Quoted 1 line · Clark Williams
Are there any guidelines or best-practices for sharing StGit trees?
See below. ;-)
Quoted 7 lines
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 :).
Quoted 8 lines
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?
You've probably already found this and dismissed it, but
$ stg uncommit foo bar baz woo wee aaahh
will uncommit six patches and give them those names. So if you just share the output of
$ stg series --applied --noprefix
along with your branch, the other end will be able to recreate a series with the same names. (In not-quite-bleeding-edge stg's, "series --applied" is spelled "applied".)
As for merging your work once both of you have made changes to the series, the current solution is "stg sync", which you'll have to ask Catalin about. The patch stack log in my experimental branch is designed to allow for true 3-way merging of patch series, so that you'd be able to get your colleague's latest modifications with a simple "stg merge" command, but that merge currently exists only in a couple of mails to this list -- there isn't even a prototype implementation -- so I expect you'll have more luck with "stg sync" right now ...
Signature · 2 lines
Karl Hasselström, [email protected] www.treskal.com/kalle
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 26 lines · Karl Hasselström
Quoted 1 line · Clark Williams
Are there any guidelines or best-practices for sharing StGit trees?
See below. ;-)
Quoted 7 lines
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 :).
Quoted 8 lines
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?
You've probably already found this and dismissed it, but
$ stg uncommit foo bar baz woo wee aaahh
Quoted 8 lines
will uncommit six patches and give them those names. So if you just share the output of
$ stg series --applied --noprefixalong with your branch, the other end will be able to recreate a series with the same names. (In not-quite-bleeding-edge stg's, "series --applied" is spelled "applied".)
Ahhhh, no I hadn't found this. Cool! I wonder if I could save the series in the branch, so that someone could just checkout the branch and do:
$ stg uncommit $(cat stg-series)
Or, maybe I'll look at adding a --series or --file option to uncommit?
I suspect some chicken-and-egg problems here, but this is workable. And when you're talking >500 patches, anything you can do to automate is a wonderful thing :).
Quoted 11 lines
As for merging your work once both of you have made changes to the series, the current solution is "stg sync", which you'll have to ask Catalin about. The patch stack log in my experimental branch is designed to allow for true 3-way merging of patch series, so that you'd be able to get your colleague's latest modifications with a simple "stg merge" command, but that merge currently exists only in a couple of mails to this list -- there isn't even a prototype implementation -- so I expect you'll have more luck with "stg sync" right now ...
Most of the time it's not more than one or two patches difference, so I think that it can be handled manually for now. I'll definitely keep an eye on sync and merge though...
Thanks,
Clark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAkjKY2cACgkQqA4JVb61b9cVYgCfZE8//UgP11+D3AKMCsDGN8Qs KpsAni8gLlZn088lQr/1nbzQf4uKHxn/
=A6MK
-----END PGP SIGNATURE-----
Quoted 5 lines · Clark Williams
Ahhhh, no I hadn't found this. Cool! I wonder if I could save the series in the branch, so that someone could just checkout the branch and do:
$ stg uncommit $(cat stg-series)
The patch stack log contains all the required info, so this should be doable (given that you share your <branchname>.stgit branch, which is the patch stack log).
Quoted 2 lines
Or, maybe I'll look at adding a --series or --file option to uncommit?
Sure, that sounds like a good idea. I believe there are existing commands that take a series file argument; check what they call their flag.
Quoted 3 lines
I suspect some chicken-and-egg problems here, but this is workable. And when you're talking >500 patches, anything you can do to automate is a wonderful thing :).
Nice to know StGit is being used with series of that size. I usually never go beyond about 30 myself, so there are certain types of scalability problems that I won't see.
Signature · 2 lines
Karl Hasselström, [email protected] www.treskal.com/kalle
Quoted 2 lines · Clark Williams
Most of the time it's not more than one or two patches difference, so I think that it
can be handled manually for now. I'll definitely keep an eye on sync and merge though...
As Karl said, we have some plans to allow collaboration between multiple StGit repositories but we didn't have much time to look at it recently. Karl's "merge" stuff looks promising though.
What "sync" does is that it allow the same set of patches between two branches to be synchronised in case modifications happened on one of these branches. In your situation, you would have to fetch the remote branch, uncommit as in Karl's method and either import or sync the remote patches with those on your local branch.
Signature · 1 line
Catalin
Quoted 9 lines · Catalin Marinas
Quoted 2 lines · Clark Williams
Most of the time it's not more than one or two patches difference, so I think that it
can be handled manually for now. I'll definitely keep an eye on sync and merge though...As Karl said, we have some plans to allow collaboration between
multiple StGit repositories but we didn't have much time to look at it recently. Karl's "merge" stuff looks promising though.
Quoted 5 lines
What "sync" does is that it allow the same set of patches between two branches to be synchronised in case modifications happened on one of these branches. In your situation, you would have to fetch the remote branch, uncommit as in Karl's method and either import or sync the remote patches with those on your local branch.
BTW, "sync" allows synchronisation with a series of patches stored in a directory. So you can also share patches using exported repositories with import and sync.
Signature · 1 line
Catalin