On Sat, Aug 18, 2018 at 03:08:21PM -0700, Jonathan Nieder wrote:
> > So we don't get to say "you never asked us about git-annex, we're using
> > that name now" without considering how widely used it is. It's us who
> > decided to expose the API of seamlessly integrating 3rd party tools.
>
> I thi
(+ git-dit authors)
Kyle Meyer wrote:
> Jonathan Nieder writes:
>> I believe you're thinking of TicGit[1].
>>
>> Some other related work is listed at [2]. Most of these projects have
>> gone quiet:
>>
>> - ditz[3]
>> - git-issues[4]
>> - cil[5]
>> - Bugs Everywhere[6]
>> - milli by Steve Kemp, w
[+cc Stefan Monnier]
Jonathan Nieder writes:
> (cc-ing Scott)
[...]
> I believe you're thinking of TicGit[1].
>
> Some other related work is listed at [2]. Most of these projects have
> gone quiet:
>
> - ditz[3]
> - git-issues[4]
> - cil[5]
> - Bugs Everywhere[6]
> - milli by Steve Kemp, whic
On Sat, Aug 18, 2018 at 3:50 PM Jonathan Nieder wrote:
> (cc-ing Elijah Newren for the points about merging)
> [...]
> > Git doesn't provide a low-level command to rebase a branch onto
> > another without touching the index.
>
> Thanks for pointing this out. There's been some recent work to make
(cc-ing Scott)
Hi Junio,
Junio C Hamano wrote:
> Michael Muré writes:
>> I released today git-bug, a distributed bug tracker that embeds in
>> git. It use git's internal storage to store bugs information in a way
>> that can be merged without conflict. You can push/pull to the normal
>> git remo
> There's been some recent work to make
> Git's merge code (also used for cherry-pick) less reliant on the index
> and worktree.
Yes please ! In the mean time, someone suggested another trick [0].
> Can you say more about the federation model it intends to support?
My goal is to have a workflow
Here was my reasoning for the naming choice:
- I need something meaningful
- I need something that encompass the idea and features of a bug
tracker because the narrower ideas and actions will be in sub commands
- other projects already used other words, in particular "issue"
- it kind of sounds an
(cc-ing Elijah Newren for the points about merging)
Hi again,
To avoid the other thread shadowing more important things:
Michael Muré wrote:
> Someone suggested in the Hacker News thread [0] to post it here as well.
Thanks to Ævar for that.
[...]
> git-bug use as identifier the hash of the fir
Ævar Arnfjörð Bjarmason wrote:
> I'm just pointing out in the more general case that if someone comes up
> with a badly named git-xyz it doesn't scale to try to point this out to
> them before git-xyz is widely deployed.
>
> So we must either let it go (solution #1), or come up with some
> API-lev
On Sat, Aug 18 2018, Jonathan Nieder wrote:
> Ævar Arnfjörð Bjarmason wrote:
>
>> The reason I can drop a "git-whatever" in my $PATH and invoke it as "git
>> whatever" is just a historical accident of how git was implemented.
>
> No. This is a very deliberate design decision, to allow people to
Ævar Arnfjörð Bjarmason wrote:
> The reason I can drop a "git-whatever" in my $PATH and invoke it as "git
> whatever" is just a historical accident of how git was implemented.
No. This is a very deliberate design decision, to allow people to
prototype new Git commands (and to create the kind of
On Sat, Aug 18 2018, Jonathan Nieder wrote:
> Hi,
>
> Ævar Arnfjörð Bjarmason wrote:
>> On Sat, Aug 18 2018, Jonathan Nieder wrote:
>>> Michael Muré wrote:
>
I released today git-bug, a distributed bug tracker
> [...]
>>> I am a bit unhappy about the namespace grab. Not for trademark
>>> r
Hi,
Ævar Arnfjörð Bjarmason wrote:
> On Sat, Aug 18 2018, Jonathan Nieder wrote:
>> Michael Muré wrote:
>>> I released today git-bug, a distributed bug tracker
[...]
>> I am a bit unhappy about the namespace grab. Not for trademark
>> reasons: the Git trademark rules are pretty clear about this
Michael Muré writes:
> I released today git-bug, a distributed bug tracker that embeds in
> git. It use git's internal storage to store bugs information in a way
> that can be merged without conflict. You can push/pull to the normal
> git remote you are already using to interact with other people
On Sat, Aug 18 2018, Jonathan Nieder wrote:
> Hi,
>
> Michael Muré wrote:
>
>> I released today git-bug, a distributed bug tracker that embeds in
>> git. It use git's internal storage to store bugs information in a way
>> that can be merged without conflict. You can push/pull to the normal
>> gi
Hi,
Michael Muré wrote:
> I released today git-bug, a distributed bug tracker that embeds in
> git. It use git's internal storage to store bugs information in a way
> that can be merged without conflict. You can push/pull to the normal
> git remote you are already using to interact with other peo
I really like this idea. I've often wanted an integrated bug database like
this. My solution has always been to have a subrepo storing bug reports and
coments in .txt files and then using bash porcelain scripts to make a git-like
interface. I think I like this better. My only nit is Go. That mak
Hi everyone,
I released today git-bug, a distributed bug tracker that embeds in
git. It use git's internal storage to store bugs information in a way
that can be merged without conflict. You can push/pull to the normal
git remote you are already using to interact with other people. Normal
code and
18 matches
Mail list logo