Having a tarball would make my life easier. I have no opinion on 0.16 vs 0.15.n
This is because debian tries to use upstream release numbers, but also depends on those numbers increasing monotonically. I could refer to a git commit, but then that package wouldn't sort between 0.15 and 0.16. Incidentally, I'm encountering some errors building the docs with asciidoc 8.6.6. I'll send patches later this week. Thanks, bergey On Sun, 8 Jan 2012 22:19:07 +0000, Catalin Marinas <[email protected]> wrote: > On 8 January 2012 13:58, Karl Wiberg <[email protected]> wrote: > > On Sat, Jan 7, 2012 at 03:35, Daniel Bergey <[email protected]> wrote: > >> I'm planning to package an updated version of stgit for Debian. I'd > >> like to use something more recent than the 0.15 release. Can someone > >> recommend a good choice? The 0.15-dirty tarball? HEAD as of today? > > That's great. Thanks. > > > I've been using > > > > 507b64d Don't clear the list of changed patches when we hit a push conflict > > Even current HEAD looks ok, I've been using it for a while (there are > some UI changes with the status command). > > Unfortunately, my aim of converting all commands to the new > infrastructure before a new release delayed a 0.16 indefinitely (and I > can't find much spare time to continue the conversion). If it helps, I > can tag the current master as 0.16 and push some release tarballs. > Thoughts? > > -- > Catalin _______________________________________________ stgit-users mailing list [email protected] https://mail.gna.org/listinfo/stgit-users
