Re: [PATCH] kernel-docs.rst: update broken linuxjournal links

2017-12-04 Thread Duy Nguyen
On Sat, Dec 2, 2017 at 10:39 PM, Jonathan Corbet wrote: > On Thu, 30 Nov 2017 17:47:25 +0700 > Nguyễn Thái Ngọc Duy wrote: > >> Signed-off-by: Nguyễn Thái Ngọc Duy >> --- >> Documentation/process/kernel-docs.rst | 14 +++---

Re: [PATCH] kernel-docs.rst: update broken linuxjournal links

2017-12-04 Thread Duy Nguyen
On Sat, Dec 2, 2017 at 10:39 PM, Jonathan Corbet wrote: > On Thu, 30 Nov 2017 17:47:25 +0700 > Nguyễn Thái Ngọc Duy wrote: > >> Signed-off-by: Nguyễn Thái Ngọc Duy >> --- >> Documentation/process/kernel-docs.rst | 14 +++--- >> 1 file changed, 7 insertions(+), 7 deletions(-) >

Re: [ANNOUNCE] Git v1.8.5-rc0

2013-11-01 Thread Duy Nguyen
On Thu, Oct 31, 2013 at 5:17 AM, Junio C Hamano wrote: > * Magic pathspecs like ":(icase)makefile" that matches both >Makefile and makefile can be used in more places. ":(glob)foo/**/bar" is another nice thing that could be announced. -- Duy -- To unsubscribe from this list: send the line

Re: [ANNOUNCE] Git v1.8.5-rc0

2013-11-01 Thread Duy Nguyen
On Thu, Oct 31, 2013 at 5:17 AM, Junio C Hamano gits...@pobox.com wrote: * Magic pathspecs like :(icase)makefile that matches both Makefile and makefile can be used in more places. :(glob)foo/**/bar is another nice thing that could be announced. -- Duy -- To unsubscribe from this list:

Re: [PATCH] commit: Add -f, --fixes option to add Fixes: line

2013-10-31 Thread Duy Nguyen
On Fri, Nov 1, 2013 at 12:20 AM, Junio C Hamano wrote: > Duy Nguyen writes: > >> OK how about, if $GIT_DIR/hooks/something is a directory, then the >> directory must contain a file named "index", listing all the hooks of >> type "something"

Re: [PATCH] commit: Add -f, --fixes option to add Fixes: line

2013-10-31 Thread Duy Nguyen
On Thu, Oct 31, 2013 at 1:12 AM, Johan Herland wrote: > Yes, we do lack a good infrastructure for managing Git hooks from > multiple sources. It makes people afraid to use them, because they > might conflict with hooks from another source. There are (off the top > of my head): > > - "personal"

Re: [PATCH] commit: Add -f, --fixes commit option to add Fixes: line

2013-10-31 Thread Duy Nguyen
On Thu, Oct 31, 2013 at 1:12 AM, Johan Herland jo...@herland.net wrote: Yes, we do lack a good infrastructure for managing Git hooks from multiple sources. It makes people afraid to use them, because they might conflict with hooks from another source. There are (off the top of my head): -

Re: [PATCH] commit: Add -f, --fixes commit option to add Fixes: line

2013-10-31 Thread Duy Nguyen
On Fri, Nov 1, 2013 at 12:20 AM, Junio C Hamano gits...@pobox.com wrote: Duy Nguyen pclo...@gmail.com writes: OK how about, if $GIT_DIR/hooks/something is a directory, then the directory must contain a file named index, listing all the hooks of type something. All the hooks in index

Re: [PATCH] commit: Add -f, --fixes option to add Fixes: line

2013-10-27 Thread Duy Nguyen
On Sun, Oct 27, 2013 at 8:34 AM, Josh Triplett wrote: > Add a command line option for git commit to automatically construct the > "Fixes:" line for a commit. This avoids the need to manually construct > that line by copy-pasting the commit hash and subject. But you still have to copy/paste the

Re: [PATCH] commit: Add -f, --fixes commit option to add Fixes: line

2013-10-27 Thread Duy Nguyen
On Sun, Oct 27, 2013 at 8:34 AM, Josh Triplett j...@joshtriplett.org wrote: Add a command line option for git commit to automatically construct the Fixes: line for a commit. This avoids the need to manually construct that line by copy-pasting the commit hash and subject. But you still have to