From: "Santi Béjar" <santi@agolina.net>
To: bamakhrama@gmail.com
Cc: Git <git@vger.kernel.org>
Subject: Re: ".dirty" suffix when building git from the source code
Date: Tue, 20 Oct 2009 14:06:32 +0200 [thread overview]
Message-ID: <adf1fd3d0910200506q7ef95823qe461e77f8ce827be@mail.gmail.com> (raw)
In-Reply-To: <40378e40910200459i14b06002k1b805936e39b5022@mail.gmail.com>
On Tue, Oct 20, 2009 at 1:59 PM, Mohamed Bamakhrama
<bamakhrama@gmail.com> wrote:
> Hi all,
>
> I have cloned the git repository and built the v1.6.4.4 tag. The
> compilation went OK and I got the tool up and running. However, when I
> generate patches, I see that the tool comments the patches with
> "1.6.4.4.dirty".
>
> My question is: what is the meaning of the ".dirty" suffix?
It says that the git source code was modified when git was compiled.
HTH,
Santi
prev parent reply other threads:[~2009-10-20 12:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 11:59 ".dirty" suffix when building git from the source code Mohamed Bamakhrama
2009-10-20 12:06 ` Santi Béjar [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=adf1fd3d0910200506q7ef95823qe461e77f8ce827be@mail.gmail.com \
--to=santi@agolina.net \
--cc=bamakhrama@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).