Paul Wise writes:
> It definitely wouldn't be appropriate to add screen scraping and
> parsing of different version control systems to myrepos.
Huh? If the tool claims to support VCS X and Y and Z, it needs to
know how to cause X and Y and Z to "fetch" in their own ways, and it
needs to know ho
On Sun, 2015-10-25 at 11:34 -0700, Junio C Hamano wrote:
> I ignored your patch when you sent it the first time the last week,
> due to the same issues I had with this round (see below) and forgot
> about it.
Thanks for the feedback this round.
> I cannot tell if you are trying to say if that i
Paul Wise writes:
I ignored your patch when you sent it the first time the last week,
due to the same issues I had with this round (see below) and forgot
about it.
> By default when fetching one remote nothing is printed unless there
> are changes that need fetching. This makes fetching multiple
By default when fetching one remote nothing is printed unless there
are changes that need fetching. This makes fetching multiple remotes
be just as verbose as fetching a single remote.
This is needed when fetching multiple repositories using the myrepos
tool in minimal output mode, where myrepos o
By default when fetching one remote nothing is printed unless there
are changes that need fetching. This makes fetching multiple remotes
be just as verbose as fetching a single remote.
This is needed when fetching multiple repositories using the myrepos
tool in minimal output mode, where myrepos o
5 matches
Mail list logo
