Am 8/31/2013 21:27, schrieb Felipe Contreras:
On Fri, Aug 30, 2013 at 2:56 AM, Johannes Sixt j.s...@viscovery.net wrote:
Am 8/30/2013 8:32, schrieb Junio C Hamano:
If you have a history where
- branches master and maint point at commit A;
- branch next points at commit B that is a
On Mon, Sep 2, 2013 at 1:25 AM, Johannes Sixt j.s...@viscovery.net wrote:
Am 8/31/2013 21:27, schrieb Felipe Contreras:
On Fri, Aug 30, 2013 at 2:56 AM, Johannes Sixt j.s...@viscovery.net wrote:
Am 8/30/2013 8:32, schrieb Junio C Hamano:
If you have a history where
- branches master and
On Fri, Aug 30, 2013 at 2:56 AM, Johannes Sixt j.s...@viscovery.net wrote:
Am 8/30/2013 8:32, schrieb Junio C Hamano:
If you have a history where
- branches master and maint point at commit A;
- branch next points at commit B that is a descendant of A; and
- there are tags X and Y
On Fri, Aug 30, 2013 at 1:32 AM, Junio C Hamano gits...@pobox.com wrote:
Felipe Contreras felipe.contre...@gmail.com writes:
So that it's possible to remove certain refs from the list without
removing the objects that are referenced by other refs.
For example this repository:
* 374e8dd
On Fri, Aug 30, 2013 at 2:11 AM, Johannes Sixt j.s...@viscovery.net wrote:
Am 8/30/2013 7:00, schrieb Felipe Contreras:
So that it's possible to remove certain refs from the list without
removing the objects that are referenced by other refs.
For example this repository:
* 374e8dd (crap)
On Fri, Aug 30, 2013 at 2:26 AM, Junio C Hamano gits...@pobox.com wrote:
Pardon terseness, typo and HTML from a tablet.
On Aug 30, 2013 12:19 AM, Felipe Contreras felipe.contre...@gmail.com
wrote:
On Fri, Aug 30, 2013 at 1:32 AM, Junio C Hamano gits...@pobox.com wrote:
Felipe Contreras
Am 8/30/2013 8:32, schrieb Junio C Hamano:
If you have a history where
- branches master and maint point at commit A;
- branch next points at commit B that is a descendant of A; and
- there are tags X and Y pointing at commits that are ahead of B
or behind A
i.e.
Am 8/30/2013 9:32, schrieb Felipe Contreras:
On Fri, Aug 30, 2013 at 2:26 AM, Junio C Hamano gits...@pobox.com wrote:
On Aug 30, 2013 12:19 AM, Felipe Contreras felipe.contre...@gmail.com
Would the same argument apply to
next ^maint --except maint
where next gets in the queue, maint in
Felipe Contreras felipe.contre...@gmail.com writes:
If you do 'master ^maint --except master', handle_commit will return
three commits:
Would the same argument apply to
next ^maint --except maint
where next gets in the queue, maint in tainted, and skipped?
maint is not skipped, as
On Fri, Aug 30, 2013 at 11:48 AM, Junio C Hamano gits...@pobox.com wrote:
Which means that the approach taken by the patch to only allow
exclusion of negative ones makes the idea only 50% useful compared
to its potential. And I suspect that we can start from 50% which
is better than 0% and
On Fri, Aug 30, 2013 at 12:00 AM, Felipe Contreras
felipe.contre...@gmail.com wrote:
So that it's possible to remove certain refs from the list without
removing the objects that are referenced by other refs.
For example this repository:
* 374e8dd (crap) crap
* 4cbbf7b (test) two
*
11 matches
Mail list logo
