Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14174
| From | Vladimir Marek <Vladimir.Marek@oracle.com> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: Bash patches format |
| Date | 2018-05-30 13:09 +0200 |
| Message-ID | <mailman.798.1527683207.1292.bug-bash@gnu.org> (permalink) |
| References | <CADv8-ohtoJJWDUuo9goOXhNORuVJSci+oi1VEygM5JSijcfZ2w@mail.gmail.com> <20180530070456.p36falhq66wfgxqk@proprietary-killer> |
> > > > If people are willing to do the conversion between patch formats for > > > their > > > > own purposes, more power to them. I don't see any compelling reason to > > > > change the format I use. > > > > > > > Could I at least convince you to start doing -p1, if not unified? > > > > > > > I think the cost is too high. All bash package maintainers on different > > *nix systems will have to change accordingly. > > > Well how about this; we ask the downstreams. List taken from repology, > hopefully these are still all active and accurate. So, to reiterate the > original premise of this thread for the newly added, I suggest the > following: Speaking for myself, as a bash maintainer in Solaris, I'm glad for Chet's work in any shape or form. And I vote for anything which makes his work easier. The rest can be scripted Thank you -- Vlad
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: Bash patches format Vladimir Marek <Vladimir.Marek@oracle.com> - 2018-05-30 13:09 +0200
csiph-web