On Mon, Sep 22, 2008 at 07:32:50PM +0200, Bert Wesarg wrote:
> On Mon, Sep 22, 2008 at 17:36, Petr Baudis <pasky@xxxxxxx> wrote:
> > Hi,
> >
> > On Fri, Sep 19, 2008 at 11:55:00AM +0200, Bert Wesarg wrote:
> >> I hacked 3 commands to explore the dependencies of TopGit patches:
> >
> > thanks, the idea of all three commands is good,
> >
> >> I) tg prev [NAME]
> >> outputs the dependencies of NAME
> >>
> >> II) tg next [NAME]
> >> outputs patches that depends on NAME
> >
> > but I think it would be cleaner to add this functionality to
> > tg info...
> Right, but 'tg next' is shorter than any 'tg info --next'.
So, an alias? ;-) I wouldn't really like to clutter the UI with many
trivial commands for getting various sort of info. And I mean, ideally
you could just see all this in default 'tg info' output (or for
computationally expensive operations, maybe 'tg info -l'?).
> >
> >> III) tg tsort [PATTERN]
> >> outputs a topological order of all patches starting with PATTERN
> >
> > ...and tg summary (overally, to have a tree view of branches).
> Maybe something like the graph output from git rev-log --graph?
That would be excellent.
> >> + printf "%s\t%q\n" "${dep_rev}" "${dep}" >&3
> >> + printf "%s\t%s\n" "${topic_rev}" "${dep_rev}"
> >
> > %q?
>
> "and %q causes printf to output the corresponding argument in a
> format that can be reused as shell input."
>
> I thought that this would be needed.
Interesting, I didn't find that in my documentation. But as said later,
this quoting is probably unnecessary.
--
Petr "Pasky" Baudis
People who take cold baths never have rheumatism,
but they have cold baths.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
