gmane.comp.version-control.git

[PATCH v3 0/3] gitweb: Optional grouping of projects by category

At Wed, 03 Dec 2008 14:51:07 -0800, Junio C Hamano wrote:

Good evening,

> I am not sure if always sorting the categories alphabetically is a
> severe enough restriction, but if it was, you can use
> @project_list_categories array that disables the feature when empty
> and otherwise enumerates the categories in order.  Just an idle
> thought.

I could add that if requested to, though Jakub seems to think
alphabetical order is also fine.  I'll be pushing v3 in a minute with
commits split by feature update and the rename to
git_get_file_or_project_config.

All this gymnastics helped me getting more familiar with add -i and
other fun workflow, thanks for the exercise[1] 

> > - When displaying a subset of all the projects, only the categories with
> >   projects in the chosen subset are displayed.
> 
> Could you clarify this bit?
> 
> It is not very clear to me how this subset selection happens.  As far as I
> can see, the user does not choose the category to view, but lets the usual
> page limiting to decide at which project to start and stop placing on the
> page

Right,

(Continue reading)

headers

Junio C Hamano | 4 Dec 01:43

Re: [PATCH v3 0/3] gitweb: Optional grouping of projects by category

Sébastien Cevey <seb <at> cine7.net> writes:

> [1] OT: I didn't find a simple command to do this:
>
>     $ git diff ..the-end-state > finish.patch
>     $ patch -p1 < finish.patch
>     $ git commit -a -s
>
>     (where the original HEAD and the-end-state have an older MRCA with
>      rewritten history inbetween, and I don't want to apply that
>      history and solve conflicts, just "get my tree to the end state".)
>
>     Any tip?

$ git read-tree -m -u the-end-state
$ git commit -a -s