Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #14177 > unrolled thread

Re: Bash patches format

Started byChet Ramey <chet.ramey@case.edu>
First post2018-05-30 09:18 -0400
Last post2018-05-30 09:18 -0400
Articles 1 — 1 participant

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Bash patches format Chet Ramey <chet.ramey@case.edu> - 2018-05-30 09:18 -0400

#14177 — Re: Bash patches format

FromChet Ramey <chet.ramey@case.edu>
Date2018-05-30 09:18 -0400
SubjectRe: Bash patches format
Message-ID<mailman.806.1527686335.1292.bug-bash@gnu.org>

[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/

[toc] | [standalone]


Back to top | Article view | gnu.bash.bug


csiph-web