> There's "branch --merged" already. And in recent versions of git, the
> scriptable for-each-ref knows it, too. So you could do something like:
>
> git for-each-ref --format='delete %(refname)' --merged HEAD refs/heads/ |
> grep -v 'any-branches-you-want-saved' |
> git update-ref --stdin
ption such as `--merged` to support
the old usecase?
--
Javier Domingo Cansino
have
to create a password for each email client on it's own. If you own a
gmail account, go to
https://security.google.com/settings/security/apppasswords to create a
password for the email client.
--
Javier Domingo Cansino
--
To unsubscribe from this list: send the line "unsubscribe
argv[i] = "@{-1}";
> + }
> +
> for (i = 0; i < rev.pending.nr; i++) {
> struct object_array_entry *entry = [i];
> struct object *obj = entry->item;
> --
> 2.7.0
>
> --
> To unsubscribe from this list: send
such
behaviour would make things harder.
--
Javier Domingo Cansino
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
also make it smart by allowing to use it as the Cisco
managing commands, or the ip tool (ip a == ip address, ip a a == ip
addr add, etc.), resulting in the following:
git ignore e
git ignore i
--
Javier Domingo Cansino
--
To unsubscribe from this list: send the line unsubscribe git
with a rebase.
Cheers,
--
Javier Domingo Cansino
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
They just have to look into the commit message and look for
#codestylefix or whatever other string.
In many projects I have seen, they have a format for commits, such as
docs: Add support for XXX, formatting: Space before parethesis and
after comas, tests: and so on.
Maybe, being able to
If you don't want an specific file, but you neither the .gitignore,
just use .git/info/exclude file for project specific or
$HOME/.config/git/ignore for user level.
Anyway, this is all in man gitignore
[1] Git ignore man page: http://git-scm.com/docs/gitignore
Javier Domingo Cansino
2014-05-26
git to
remember the commands. At the moment, git[1] just tells many of the
commands available, without any classification, maybe classifying them
as commiting branching and remote could help a little.
Regards,
Javier Domingo Cansino
[1] git output
I think it is a suitable logo. It might not be the one I would think
of, but I see with good eyes using it as one of the project logos.
Javier Domingo Cansino
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info
with.
BTW, I don't know if the old logo I am accustomed to has ever been
used by the project officially, but I always thought it was that one.
Javier Domingo Cansino
[1] Git logo: http://git-osx-installer.googlecode.com/files/GitLogo.jpg
--
To unsubscribe from this list: send the line
Will there be any change on how tarballs are distributed, taking into
account that Google will be shutting down Google Code Downloads
section[1][2]?
Cheers
Javier Domingo Cansino
[1] Google Code download service change announcement:
http://google-opensource.blogspot.se/2013/05/a-change
13 matches
Mail list logo