[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Make a "general" Emacs configuration
From: |
Glauber Alex Dias Prado |
Subject: |
Re: Make a "general" Emacs configuration |
Date: |
Thu, 12 Aug 2010 15:08:19 -0300 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) |
Tim Visher <tim.visher@gmail.com> writes:
> On Thu, Aug 12, 2010 at 9:57 AM, Andrea Crotti
> <andrea.crotti.0@gmail.com> wrote:
>> Andrea Crotti <andrea.crotti.0@gmail.com> writes:
>>>
>>> Well with git submodules is not a problem anyway, since it keeps track
>>> of the version so everyone cloning the repo will have the same version
>>> of submodules.
>>
>> But I have another problem now, whenever I do something (even just
>> byte-compilation) inside a submodule I get this
>>
>> --8<---------------cut here---------------start------------->8---
>> Submodule doxymacs contains untracked content
>> --8<---------------cut here---------------end--------------->8---
>>
>> which is a bit annoying.
>> Then the changes are not automatically staged and you would have to
>> commit explicitly, but still that "dirty" flag is not nice.
>
> $ cd path/to/submodule/root
> $ cat > .gitignore
> *.elc
> C-d
>
> That should get rid of the untracked content in your submodule in the
> case of byte compilation.
>
>> Maybe is worth to mirror everything myself, so even if I want to modify
>> something I can also push the changes, and the maybe send the patch to
>> the original author.
>
> If you're planning on modifying anything about the project, then the
> accepted way to do this in git would be to set up your own fork of the
> project to enable you to share patches and to update your own copy of
> it. Also, you'll need a commit at which to point your submodule and
> if you're going to change the submodule there's no guarantee that the
> original author will accept them so you'll need a central place to
> keep those commits.
Maybe im doing it wrong but i am branching my submodules to change
them. Would it be better to have a consumer submodule and a producer
separate repo in case i want to send a pull request? but then any change
i made will have to be accepted before i can consume it and the workflow will
kind
of become anti-productive.
- Re: Make a "general" Emacs configuration, (continued)
- Re: Make a "general" Emacs configuration, Gabriele Lanaro, 2010/08/10
- Re: Make a "general" Emacs configuration, Andrea Crotti, 2010/08/10
- Re: Make a "general" Emacs configuration, Bernardo, 2010/08/10
- Re: Make a "general" Emacs configuration, Andrea Crotti, 2010/08/11
- Re: Make a "general" Emacs configuration, Tim Visher, 2010/08/11
- Re: Make a "general" Emacs configuration, Andrea Crotti, 2010/08/11
- Re: Make a "general" Emacs configuration, Glauber Alex Dias Prado, 2010/08/11
- Re: Make a "general" Emacs configuration, Andrea Crotti, 2010/08/12
- Re: Make a "general" Emacs configuration, Andrea Crotti, 2010/08/12
- Re: Make a "general" Emacs configuration, Tim Visher, 2010/08/12
- Re: Make a "general" Emacs configuration,
Glauber Alex Dias Prado <=
- Re: Make a "general" Emacs configuration, Tim Visher, 2010/08/13
- Re: Make a "general" Emacs configuration, Glauber Alex Dias Prado, 2010/08/13
- Re: Make a "general" Emacs configuration, Andrea Crotti, 2010/08/13