On Thu, Feb 21, 2008, Guido Günther wrote:
> I'd rather not do this since it might lead to suptle errors. What about
> using a shell alias instead:
> alias gbpin="git-buildpackage --ignore-new"
> But I wonder what reason would you have to always use ignore-new? Maybe
> there's a valid one I'm not
Hi Loïc,
On Tue, Mar 18, 2008 at 09:26:37AM +0100, Loïc Minier wrote:
> I see the bug was wontfixed as the submitter explained that he simply
> should .gitignore the files.
I tagged the bug wontfix mostly to get more feedback on people's
workflows. I won't object to adding this option if it reall
> I'd rather not do this since it might lead to suptle errors. What about
> using a shell alias instead:
> alias gbpin="git-buildpackage --ignore-new"
sure...
> But I wonder what reason would you have to always use ignore-new? Maybe
> there's a valid one I'm not seeing?
well -- it is just that t
Hi Yaroslav,
On Thu, Feb 21, 2008 at 01:50:41PM -0500, Yaroslav Halchenko wrote:
> Could you please add an option to 'permanent' --git-ignore-new within
> gbp.conf (I need it for 1 gittified project to be kept in /.gbp.conf
> there).
I'd rather not do this since it might lead to suptle errors. What
Package: git-buildpackage
Version: 0.4.13~etch1
Severity: wishlist
Could you please add an option to 'permanent' --git-ignore-new within
gbp.conf (I need it for 1 gittified project to be kept in /.gbp.conf
there).
I guess it should look smth like
[git-buildpackage]
# ignore some any non-gitted
5 matches
Mail list logo
