Okay but who wants to help for the first pass? are you in?
On Fri, Jan 31, 2014 at 6:42 PM, Antoine Musso wrote:
> Le 31/01/14 13:30, Amir Ladsgroup a écrit :
> > Hi all,
> > There are 294 bugs that are unsolved, unprioritized, and unconfirmed, in
> > other words we have almost 300 bugs that no
Le 31/01/14 13:30, Amir Ladsgroup a écrit :
> Hi all,
> There are 294 bugs that are unsolved, unprioritized, and unconfirmed, in
> other words we have almost 300 bugs that no one has even touched it yet. [1]
>
> I thought about another bug triage but I have an idea, let's split it up
> the list a
it seems so
On Fri, Jan 31, 2014 at 3:12 PM, Merlijn van Deen wrote:
> Does ignore=all work?
>
>
> On 31 January 2014 13:32, Mpaa wrote:
>
>> This is mine:
>> 1 [submodule "i18n"]
>> 2 path = scripts/i18n
>> 3 url = https://gerrit.wikimedia.org/r/p/pywikibot/i18n.git
>> 4 br
Does ignore=all work?
On 31 January 2014 13:32, Mpaa wrote:
> This is mine:
> 1 [submodule "i18n"]
> 2 path = scripts/i18n
> 3 url = https://gerrit.wikimedia.org/r/p/pywikibot/i18n.git
> 4 branch = .
> 5 ignore = dirty
> 6
> 7 [submodule "externals/httplib2"]
> 8
This is mine:
1 [submodule "i18n"]
2 path = scripts/i18n
3 url = https://gerrit.wikimedia.org/r/p/pywikibot/i18n.git
4 branch = .
5 ignore = dirty
6
7 [submodule "externals/httplib2"]
8 path = ex/httplib2ternals/httplib2
9 url =
https://gerrit.wikimedia.org
Hi all,
There are 294 bugs that are unsolved, unprioritized, and unconfirmed, in
other words we have almost 300 bugs that no one has even touched it yet. [1]
I thought about another bug triage but I have an idea, let's split it up
the list and work on them. What do you think? a triage or a maratho
https://stackoverflow.com/questions/3240881/git-can-i-suppress-listing-of-modified-content-dirty-submodule-entries-in-sta
So the trick is to adapt .gitmodules, not .gitignore.
Merlijn
On 31 January 2014 09:56, Mpaa wrote:
> Hi.
>
> Is there a way to avoid having these to file to always show u
their version are different compare to the upstream content (e.g. core or
compat) for so I think it worth a try
On Fri, Jan 31, 2014 at 2:30 PM, Mpaa wrote:
> "Some files in a repository, which are versioned (i.e. they can't be
> git-ignored), ..."
> I guess those two files are versioned, so ca
"Some files in a repository, which are versioned (i.e. they can't be
git-ignored), ..."
I guess those two files are versioned, so can we git-ignore?
On Fri, Jan 31, 2014 at 11:22 AM, Amir Ladsgroup wrote:
> yes, there is a file named ".gitignore" or something like that, see it
>
> Best
>
>
> On
yes, there is a file named ".gitignore" or something like that, see it
Best
On Fri, Jan 31, 2014 at 12:26 PM, Mpaa wrote:
> Hi.
>
> Is there a way to avoid having these to file to always show up as
> non-staged?
>
> $ git status
> # On branch cat
> # Changes not staged for commit:
> # (use "
Hi.
Is there a way to avoid having these to file to always show up as
non-staged?
$ git status
# On branch cat
# Changes not staged for commit:
# (use "git add ..." to update what will be committed)
# (use "git checkout -- ..." to discard changes in working
directory)
#
# modified: ex
11 matches
Mail list logo