threads / discuss / 13178

Unresolved issues

Subject: Unresolved issues

## tl;dr

4 messages between Apr 19, 2008 and Apr 21, 2008.

replies: 3people: 4as markdown or json

Junio C Hamano· Apr 19, 2008, 08:19 UTC · lore

Here is an "issues" list I am keeping track of on the back of my head (and in "TODO" file on 'todo' branch, which is not updated often enough).

The tail end of this list is probably a bit stale, as I am running out of time tonight and did not have enough time to check the current status. Please spot issues that have been resolved and report them.

----------------------------------------------------------------

Possible bug not diagnosed yet

* "git commit --interactive" allows same tree as parent to be recorded

Message-ID: <slrng059n3.nd8.joerg@alea.gnuu.de>

----------------------------------------------------------------

Issues that are unconcluded or need a fresh infusion of kerosene to firestart them again.

* adding across symlinks (me)

Message-ID: <7vd4oppllw.fsf@gitster.siamese.dyndns.org>

* cvsserver improvements (Fredrik Noring)

Needs third-party confirmation and then properly applicable patches.

* reworking rebase interactive (Jörg Sommer)

Message-Id: <1208132469-26471-1-git-send-email-joerg@alea.gnuu.de>
Message-Id: <1208169584-15931-1-git-send-email-joerg@alea.gnuu.de>

* log --graph (Adam Simpkins)

Message-ID: <20080406214445.GA5822@adamsimpkins.net>

* --pretty=format:%d (Dscho)

* SP in path to $GIT_DIR breaks some scripts and many tests (Bryan Donlan)

Message-ID: <20080410084820.GA1904@shion.is.fushizen.net>

* Prepare cvsimport for fixed cvsps (David Mansfield)

Message-Id: <1207100091.10532.64.camel@gandalf.cobite.com>

* ff=only (Sverre Hvammen Johansen)
  $gmane/78250

* more help backends (Christian Couder)
  $gmane/78150

* cvsserver updates (Damien Diederen with help by Frank Lichtenheld)
  $gmane/78188

* rewriting annotated tags in filter-branch (Brandon Casey)
  $gmane/78286

* fsck --lost-found (me)
  $gmane/78267

* core.inithook (Dscho)
  $gmane/78123

* receive.localBranches = { refuse | allow } (Dscho)
  $gmane/78065

* autosetting core.ignorecase (Dmitry Potapov)
  $gmane/78176

* mailinfo extention to extract Message-ID and others (Anton Gladkov)
  $gmane/78006

* rebase -p
  $gmane/78074

  There is a quite well done series from Jörg Sommer I have to queue but
  I am getting the feeling that it did not get enough review from the
  list.  I am reading it through (slowly) myself, but I'd appreciate more
  review comments on the list (not limited to this series).

* synopsys: use {} instead of () for grouping alternatives (Jari Aalto)
  $gmane/72243

* "[alias] st = status" and "cd .git && git st" (Jeff King)
  $gmane/72327

* "git fetch" does not exit with non-zero status when it failed to update
  some refs due to non-ffness (Daniel)
  $gmane/77178

* use "assume unchanged" bit to implement narrow checkout
  $gmane/77046

* zlib abstraction (Marco)
  $gmane/72262

* git --index-file=<foo> <cmd> (Linus)
  $gmane/77332

* git lost-found vs git fsck --lost-found
  $gmane/78267

Teemu Likonen· Apr 20, 2008, 15:48 UTC · re: Junio C Hamano · lore

Re: Unresolved issues, "log --graph"

Junio C Hamano wrote (2008-04-19 01:19 -0700):

> Here is an "issues" list I am keeping track of on the back of my head
> (and in "TODO" file on 'todo' branch, which is not updated often
> enough).

> * log --graph (Adam Simpkins)

Hi Adam, any changes for modifying the "log --graph" patch series to make it apply to the current development version of git? It would just feel wrong if this apparently well-designed tool was left behind. Of course it's up to you.

Some thoughts on the graph functionality: I have understood that many Bazaar people like the way "bzr log" indents the log entries which originate from other branches. This way Bazaar users can easily think in terms of commits in the mainline and commits originating from feature branches. I think this is useful distinction sometimes.

I just realised that Adam's "git log --graph" offers the same functionality as "bzr log" but much better. With "git log --graph" user can see the history the way "bzr log" displays it: the current branch is on the leftmost graph line and can be seen as the "mainline" (if wanted); commits coming from other branches are indented and appear in separate graph lines. Yes, there is, and have been, "gitk" of course. "log --graph" is just much closer to "bzr log" view. I think "git log" is quite superiour as it allows many ways of viewing history.

Adam Simpkins· Apr 21, 2008, 17:33 UTC · re: Teemu Likonen · lore

Re: Unresolved issues, "log --graph"

On Sun, Apr 20, 2008 at 06:48:48PM +0300, Teemu Likonen wrote:

Show 12 quoted lines

> Junio C Hamano wrote (2008-04-19 01:19 -0700):
> 
> > Here is an "issues" list I am keeping track of on the back of my head
> > (and in "TODO" file on 'todo' branch, which is not updated often
> > enough).
> 
> > * log --graph (Adam Simpkins)
> 
> Hi Adam, any changes for modifying the "log --graph" patch series to
> make it apply to the current development version of git? It would just
> feel wrong if this apparently well-designed tool was left behind. Of
> course it's up to you.

Yes. I didn't mean to drop this, I've just haven't had much time to work on it lately. I may get a chance to work on it tomorrow, otherwise I'll do it this coming weekend.

I'll submit a new series of patches to apply the "log --graph" changes onto master. I think the only thing that needs to be changed is to update my code to work with Junio's jc/terminator-separator changes. It looks like it should be fairly straightforward.

Junio and others, is there anything else I should do to make the "log --graph" changes ready for pu/next/master?

-- 
Adam Simpkins
adam@adamsimpkins.net

Johannes Schindelin· Apr 21, 2008, 17:59 UTC · re: Adam Simpkins · lore

Re: Unresolved issues, "log --graph"

Hi,

On Mon, 21 Apr 2008, Adam Simpkins wrote:

Show 25 quoted lines

> On Sun, Apr 20, 2008 at 06:48:48PM +0300, Teemu Likonen wrote:
> > Junio C Hamano wrote (2008-04-19 01:19 -0700):
> > 
> > > Here is an "issues" list I am keeping track of on the back of my head
> > > (and in "TODO" file on 'todo' branch, which is not updated often
> > > enough).
> > 
> > > * log --graph (Adam Simpkins)
> > 
> > Hi Adam, any changes for modifying the "log --graph" patch series to
> > make it apply to the current development version of git? It would just
> > feel wrong if this apparently well-designed tool was left behind. Of
> > course it's up to you.
> 
> Yes.  I didn't mean to drop this, I've just haven't had much time to
> work on it lately.  I may get a chance to work on it tomorrow,
> otherwise I'll do it this coming weekend.
> 
> I'll submit a new series of patches to apply the "log --graph" changes
> onto master.  I think the only thing that needs to be changed is to
> update my code to work with Junio's jc/terminator-separator changes.
> It looks like it should be fairly straightforward.
> 
> Junio and others, is there anything else I should do to make the "log
> --graph" changes ready for pu/next/master?

I look forward to it!

Ciao, Dscho