, I'm saying that well-named
branches can and do carry useful contextual information that oughtn't to
be thrown away. Currently, when you delete that branch, you lose the
branch name altogether.
So what do you think? Would it be good to have a patch to add this feature?
--
Best regards,
Jeremy
you can link a commit to in an
issue tracker. You may just be implementing a feature that has been
agreed upon, independently of any such tracker. In that case, there's
no bug# to link to.
--
Best regards,
Jeremy Morton (Jez)
--
To unsubscribe from this list: send the line unsubscribe git
commits, which is rather undesirable when you
could just see the branch name (when perusing 'git log') if it were
tagged as part of the commit.
Hope this helps,
...Johan
--
Best regards,
Jeremy Morton (Jez)
--
To unsubscribe from this list: send the line unsubscribe git in
the body
referenced.)
Well, as I said elsewhere in this discussion, Git should provide that
functionality built-in, IMHO. It would be good to be able to set a
one-liner in my .gitconfig to tag each commit with a branch checked
into trailer.
--
Best regards,
Jeremy Morton (Jez)
--
To unsubscribe from
a handy short description of what
part of the application this branch is modifying (like my
pacman-minigame example).
--
Best regards,
Jeremy Morton (Jez)
--
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
of the audit record, though? Aren't
you just arbitrarily defining them as part of the audit record?
--
Best regards,
Jeremy Morton (Jez)
--
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
as a hook on a per-repo basis. Do you foresee a point in
the future where these trailers could be added through simple one-liners
in someone's global .gitconfig file? That's where I'd really like to
get to.
--
Best regards,
Jeremy Morton (Jez)
--
To unsubscribe from this list: send the line
, or what group of
commits it is a part of.
--
Best regards,
Jeremy Morton (Jez)
--
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
the co-workers need to run the post-checkout hook
script manually the first time?
--
Best regards,
Jeremy Morton (Jez)
--
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
On 28/04/2014 10:01, Felipe Contreras wrote:
Jeremy Morton wrote:
On 27/04/2014 20:33, Johan Herland wrote:
The problem is not really less tidy commit trees - by which I gather
you mean history graphs that are non-linear. IMHO, the history graph
should reflect parallel/branched development
On 28/04/2014 10:17, Felipe Contreras wrote:
I don't seem to what? I'm the one arguing for change, and I sent the patches to
fix this default behavior.
Well maybe you should work on phrasing things better - you come across
as quite negative.
--
Best regards,
Jeremy Morton (Jez
. And also how about some logic to be able to say that
if you're committing to the master branch, the trailer doesn't get
inserted at all?
--
Best regards,
Jeremy Morton (Jez)
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More
that too.
But it would be nicer if the logic were built-in, then you wouldn't have
to share some script with your work colleagues. :-)
--
Best regards,
Jeremy Morton (Jez)
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More
that too.
But it would be nicer if the logic were built-in, then you wouldn't have
to share some script with your work colleagues. :-)
--
Best regards,
Jeremy Morton (Jez)
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More
? Is there an easier way to do this?
--
Best regards,
Jeremy Morton (Jez)
--
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
Junio C Hamano gitster at pobox.com writes:
Jeremy Morton admin at game-point.net writes:
I've noticed that the p4merge shell script could do with some
improvement when it comes to merging. Because p4merge throws up an
error when one of the files it's given to diff is /dev/null, git
installation here?
--
Best regards,
Jeremy Morton (Jez)
--
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
regards,
Jeremy Morton (Jez)
On 11/10/2012 04:22, David Aguilar wrote:
p4merge does not properly handle the case where /dev/null
is passed as a filename.
Workaround it by creating a temporary file for this purpose.
Reported-by: Jeremy Mortonad...@game-point.net
Signed-off-by: David Aguilardav
g option that
allows the user to say that this should happen.
--
Best regards,
Jeremy Morton (Jez)
--
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
rome
is for. We're talking about Git users using the commandline client.
They ought to know what they're doing and if they don't, they're
screwed anyway because there are quite a few gotchas with Git.
--
Best regards,
Jeremy Morton (Jez)
--
To unsubscribe from this list: send the line "uns
(supposedly unrelated) somewhere
else changes and you didn't remember and you tear your hair out.
Not when it reduces useful functionality for experts, it's not.
--
Best regards,
Jeremy Morton (Jez)
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message
On 10/11/2015 18:12, Stefan Beller wrote:
On Tue, Nov 10, 2015 at 8:31 AM, Jeremy Morton<ad...@game-point.net> wrote:
It's recently come to my attention that the "git alias" config functionality
ignores all aliases that would override existing Git commands. This seems
like
that there is *still* no way for me
to configure git (on a global, not per-repo basis) to automatically
tack a trailer onto every commit message? For the record, I want that
trailer to be the current branch name.
--
Best regards,
Jeremy Morton (Jez)
--
To unsubscribe from this list: send
Yeah but it's kind of useless to me having it on each commit on a
per-repo basis (and even then, only with hooks).
--
Best regards,
Jeremy Morton (Jez)
On 28/08/2015 18:06, Junio C Hamano wrote:
Jeremy Mortonad...@game-point.net writes:
I see that interpret-trailers has been added
Did this ever get anywhere? Can we recursively update submodules with
"git pull" in the supermodule now?
--
Best regards,
Jeremy Morton (Jez)
On 04/06/2014 10:30, Chris Packham wrote:
Add a config option that will cause clone to recurse into submodules as
if the --recurse-submodu
the option of referencing a submodule's branch instead of a given
submodule commit. How about adding this functionality?
--
Best regards,
Jeremy Morton (Jez)
it
module configuration.
--
Best regards,
Jeremy Morton (Jez)
Did this ever get anywhere? If not why not? It would be very useful
to me to be able to clone recursively by default, especially
considering you can't use 'alias' to override the existing 'clone'
command.
--
Best regards,
Jeremy Morton (Jez)
On 06/06/2014 06:26, Heiko Voigt wrote:
On Thu
I discovered it was an issue with the version of Git for Windows I was
using. Upgraded to the latest version and it works now.
--
Best regards,
Jeremy Morton (Jez)
On 30/07/2018 16:37, Jeff King wrote:
On Mon, Jul 30, 2018 at 01:49:46PM +0100, Jeremy Morton wrote:
I'm trying to search my
own, repeating this output
infinitely until I hit 'q'. What is going on here??
--
Best regards,
Jeremy Morton (Jez)
30 matches
Mail list logo
