7ca3d9d71f · matheusbsbs/matheus-bagliano

@@ -14,34 +14,6 @@ to pick an item from the list and work on it.

14 Recent issues

15 -------------

16

17 -* gitweb patches (bunch of them)

18 -

19 -From: Matt McCutchen <hashproduct@gmail.com>

20 -Subject: [PATCH] gitweb: snapshot cleanups & support for offering multiple formats

21 -Message-ID: <1183053733.6108.0.camel@mattlaptop2>

22 -

23 -Subject: [PATCH] gitweb: make search form generate pathinfo-style URLs

24 -Message-ID: <1183057027.6108.4.camel@mattlaptop2>

25 -

26 -Subject: [PATCH] gitweb: make "No commits" in project list gray, not bold green

27 -Message-ID: <1183068922.6108.8.camel@mattlaptop2>

28 -

29 -From: Miklos Vajna <vmiklos@frugalware.org>

30 -Subject: [PATCH] gitweb: prefer git_get_project_owner() over get_file_owner()

31 -Message-ID: <20070703221122.GI32766@genesis.frugalware.org>

32 -

33 -From: Michael Hendricks <michael@ndrix.org>

34 -Subject: [PATCH] gitweb: configurable width for the projects list Description column

35 -Message-ID: <11835958082458-git-send-email-michael@ndrix.org>

36 -

37 -

38 -* switching branches when b changes between symlink and directory in a/b/c

39 -

40 -From: Pierre Habouzit <madcoder@debian.org>

41 -Subject: [BUG (or misfeature?)] git checkout and symlinks

42 -Message-ID: <20070704203541.GA13286@artemis.corp>

43 -

44 -

17 * cherry-pick unexpected conflicts

18

19 From: Gerrit Pape <pape@smarden.org>

@@ -49,18 +21,14 @@ Subject: Re: unexpected git-cherry-pick conflict

21 Date: Wed, 13 Jun 2007 13:43:35 +0000

22 Message-ID: <20070613134336.13661.qmail@c61f4fed932273.315fe32.mid.smarden.org>

23

52 -* git-apply -R --whitespace=warn

24 +* 3way merge still has D/F conflict problems

25

54 -From: Daniel Barkalow <barkalow@iabervon.org>

55 -Message-ID: <Pine.LNX.4.64.0707062155170.6977@iabervon.org>

56 -Subject: Minor bug in git-apply's patch-cleaning

26 +Subject: [RFH] 3way still has D/F conflict problems...

27 +Date: Mon, 23 Jul 2007 00:22:51 -0700

28 +Message-ID: <7vejizmvn8.fsf@assigned-by-dhcp.cox.net>

29

58 -* gitk --left-right

59 -

60 -From: Linus Torvalds <torvalds@linux-foundation.org>

61 -Message-ID: <alpine.LFD.0.98.0705051524300.17381@woody.linux-foundation.org>

62 -From: Junio C Hamano <junkio@cox.net>

63 -Message-ID: <7vabwifl23.fsf@assigned-by-dhcp.cox.net>

30 +I am punting on unpack-trees related D/F issues for 1.5.3. We

31 +might end up rewriting read-tree after the release.

32

33 * Pushing into a non-bare repository more gracefully.

34

@@ -90,12 +58,6 @@ Repeated requests against git-daemon makes it stuck under --syslog

58 another branch that has a file where the current branch has a

59 directory could lose such 'precious' files.

60

93 - - Customized "diff -p" markers per path.

94 -

95 - From: Linus Torvalds <torvalds@linux-foundation.org>

96 - Subject: Re: [PATCH] Per-path attribute based hunk header selection.

97 - Message-ID: <alpine.LFD.0.98.0707061051020.9434@woody.linux-foundation.org>

98 -

61 - Others???

62

63

@@ -162,43 +124,6 @@ Technical (milder)

124 Technical (trivial)

125 -------------------

126

165 -* Change the "first line of commit message is special" rule to

166 - "first paragraph" and then wrap it.

167 -

168 - From: Junio C Hamano <junkio@cox.net>

169 - Message-ID: <7vsla5pkug.fsf@assigned-by-dhcp.cox.net>

170 -

171 - This is slightly related, but I have been wondering about the

172 - interaction with "single-liner summary, empty line and then the

173 - rest" convention and various commands in the log family.

174 -

175 - Currently, --pretty=oneline and --pretty=email (hence format-patch)

176 - take and use only the first line. I think we could change it to:

177 -

178 - - take the first paragraph, where the definition of the first

179 - paragraph is "skip all blank lines from the beginning, and

180 - then grab everything up to the next empty line".

181 -

182 - - replace all line breaks with a whitespace.

183 -

184 - This change would not affect well-behaved commit messages that

185 - adhere to the convention, as their first paragraph always

186 - consist of a single line. On the other hand, people from

187 - different culture can get frustrated by their commit message

188 - chomped at the first linebreak in the middle of sentence right

189 - now, which would be helped by this change.

190 -

191 - Their Subject: and --pretty=oneline output would become very

192 - long and unsightly, but their commit messages are already

193 - ugly anyway, and such a change at least avoid the loss of

194 - information.

195 -

196 - If we were to do this, Subject: line would most likely use

197 - RFC2822 line folding at the places where line breaks were in the

198 - original, but that goes without saying.

199 -

200 - What do people think?

201 -

127 * Give --stdin to git-log, similar to git-rev-list

128

129 From: "Marco Costalba" <mcostalba@gmail.com>

TODO updates