Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14177
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: Bash patches format |
| Date | 2018-05-30 09:18 -0400 |
| Message-ID | <mailman.806.1527686335.1292.bug-bash@gnu.org> (permalink) |
| References | <20180519134601.u3dfrjzip3do7daj@proprietary-killer> <2b5ce5fe-3250-ba63-4ad7-0326ac5a5707@case.edu> <20180530002542.dpwb756slvtjgtxu@proprietary-killer> <20180530034412.GN3094@zaya.teonanacatl.net> |
[Multipart message — attachments visible in raw view] - view raw
On 5/29/18 11:44 PM, Todd Zullinger wrote: > The main difference is the lack of detail in the git commit > message. It would great if the same data found in the > bash44-019 patch file was added to the git commit message. This is certainly doable. I would just have to change the script I use. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: Bash patches format Chet Ramey <chet.ramey@case.edu> - 2018-05-30 09:18 -0400
csiph-web