Dear fast importers,
Another week, another fast-import protocol extension.
Most DVCSes do not allow one to non-disruptively change the log
message for a commit. But sometimes people want to attach information to a
commit after the fact:
- whether it was tested and worked correctly
- who liked
Heya,
On Mon, Jan 31, 2011 at 19:33, Jonathan Nieder wrote:
> Most DVCSes do not allow one to non-disruptively change the log
> message for a commit. But sometimes people want to attach information to a
> commit after the fact:
>
> - whether it was tested and worked correctly
> - who liked or
Sverre Rabbelier wrote:
> I talked with Augie Fackler (from hg) about this on IM and he says:
>> We don't support anything like that at present (no demand, when we check
>> nobody really seems to use git notes for anything)
>> so it doesn't seem relevant in fast-export
>
> So at least HG doesn't (
Heya,
On Mon, Jan 31, 2011 at 20:01, Jonathan Nieder wrote:
> Thanks, good to know. I suppose this definitely needs a feature name,
> then (I'll send a patch to make it "feature notes").
SGTM.
> [Aside: I suspect part of the reason "git notes" adoption is not so
> great is the lack of git note
On 01/02/11 10:19, Sverre Rabbelier wrote:
> That's another thing Augie mentioned that he (and I guess the hg
> community at large) dislikes, the fact that they're not propagated.
This is not a "fact".
If you add configuration in your git config to fetch and push the refs,
then they are propagate
Heya,
On Mon, Jan 31, 2011 at 23:37, Sam Vilain wrote:
> This is not a "fact".
>
> If you add configuration in your git config to fetch and push the refs,
> then they are propagated.
Heh, I was contemplating whether to add "(by default)" or not, I guess
I should have.
--
Cheers,
Sverre Rabbel
6 matches
Mail list logo
