From: Bomar_Samuel
Sent: Sunday, December 21, 2014 9:28 PM
To: Bomar_Samuel
Subject: Validera din brevlåda konto
Din brevlåda har överskridit lagringskvoten som bestäms av din
e-postadministratör, och du kommer inte att kunna ta emot stora mail tills du
åter bek
I ran across an interesting case that diffs very slowly with modern git.
And it's even public. You can clone:
git://github.com/outpunk/evil-icons
and try:
git show fc4efe426d5b4e6aa8d5a4dc14babeada7c5f899
(which is also the tip of master as of this writing).
The interesting file there is a
On Sun, Dec 21, 2014 at 10:53:35AM -0800, Reuben Hawkins wrote:
> CLOCK_MONOTONIC isn't available on RHEL3, but there are still RHEL3
> systems being used in production. This change makes compiling git
> less tedious on older platforms.
While I'm not opposed to this change, I expect that you'll f
On Mon, Dec 22, 2014 at 1:40 AM, Junio C Hamano wrote:
> What is a push refspec with an empty right-hand-side supposed to do in
> the first place anyway?
Error out. My bad.
--
Duy
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.
Hi,
As you may or may not know, I'm working on a remote-helper to interact
with mercurial servers, with the main focus being to make it work with
developer workflows at Mozilla.
I think remote-helpers, in the context of non-git remotes, can be
leveraged to improve git user experience with non-git
Jim Hill writes:
> I call it unwanted because the default works fine with the actual
> input and explicitly limiting whitespace this way breaks most command
> substitution.
OK. I'd call that "unnecessary", not "unwanted", though.
It becomes unwanted only when somebody cuts and pastes and chang
kel...@shysecurity.com writes:
>> "Philip Oakley" wrote:
>> Shouldn't this `(identical to "git diff --relative")` also be
>>included in the documentation change? It would truly clarify the
>> intenbt for the reader.
>
> Updated as follows:
> +diff.relative::
> + Show pathnames relative to the
On Sun, Dec 21, 2014 at 3:20 PM, Eric Sunshine wrote:
> On Sun, Dec 21, 2014 at 1:53 PM, Reuben Hawkins wrote:
>> +AC_CHECK_MEMBER([struct stat.st_mtim.tv_nsec],
>> +[HAVE_ST_MTIM=Yes],
>> +[HAVE_ST_MTIM=No],
>
> In Autoconf, it's customary to use lowercase values (such as "yes"
> rather than "Ye
On Sun, Dec 21, 2014 at 1:53 PM, Reuben Hawkins wrote:
> Older versions of OpenSSL have HMAC_cleanup, but not HMAC_CTX_cleanup.
> This change checks for both, uses HMAC_CTX_cleanup on platforms which
> have it, otherwise falls back to HMAC_cleanup.
On this project, imperative mood is preferred. A
On Sun, Dec 21, 2014 at 1:53 PM, Reuben Hawkins wrote:
> CLOCK_MONOTONIC isn't available on RHEL3, but there are still RHEL3
> systems being used in production. This change makes compiling git
> less tedious on older platforms.
Missing sign-off.
> ---
> diff --git a/configure.ac b/configure.ac
Hi Anastas,
On Fri, 19 Dec 2014, Anastas Dancha wrote:
> On Fri, Dec 19, 2014 at 4:37 AM, Johannes Schindelin
> wrote:
> > [...]
> > There is one bit left to clarify: let me guess, you have a $HOME/.gitconfig
> > like this:
> >
> > [url "anas...@company.com"]
> > insteadO
added support for `git diff --no-relative` (code, documentation, and tests)
git-diff --no-relative overrides diff.relative config setting and prior
git-diff --relative[=] options.
---
Documentation/diff-config.txt | 1 +
Documentation/diff-options.txt | 4 +++
diff.c
By default, git-diff shows changes and pathnames relative to the
repository root.
Setting diff.relative to "true" shows pathnames relative to the current
directory
and excludes changes outside this directory.
---
Documentation/diff-config.txt | 5 +
diff.c| 8 +
On Sun, Dec 21, 2014 at 1:53 PM, Reuben Hawkins wrote:
> This check will automatically set the correct NO_NSEC setting.
Missing sign-off. See git/Documentation/SubmittingPatches.
> ---
> diff --git a/configure.ac b/configure.ac
> index 6af9647..3cfdd51 100644
> --- a/configure.ac
> +++ b/configu
"Philip Oakley" wrote:
Shouldn't this `(identical to "git diff --relative")` also be
included in the documentation change? It would truly clarify the
intenbt for the reader.
Updated as follows:
+diff.relative::
+ Show pathnames relative to the current directory and exclude
+ changes
Limiting the shell's word splitting breaks command substitution from
e.g. `git rev-list` output, the motivating example is
range="$local_sha $(
git for-each-ref --format='^%(refname)' refs/remotes/$remote
)"
# ...
commit=`git rev-list -n 1 --grep '\bbad string\b' $range
To reproduce:
git init testrepo
cd testrepo
touch test.txt
mkdir sub
echo 'gitdir: path/to/nowhere' >> sub/.git
git gui
Displays no files/changes, no error message.
Should display test.txt in git-gui. Or possibly fail with error
(though git status does not fail).
Shell should display error messa
I call it unwanted because the default works fine with the actual
input and explicitly limiting whitespace this way breaks most command
substitution. For instance, attempting to check only new commits with
range="$local_sha $(
git for-each-ref --format='^%(refname)' refs/remotes/$
CLOCK_MONOTONIC isn't available on RHEL3, but there are still RHEL3
systems being used in production. This change makes compiling git
less tedious on older platforms.
---
configure.ac | 26 ++
trace.c | 2 +-
2 files changed, 27 insertions(+), 1 deletion(-)
diff --g
Older versions of OpenSSL have HMAC_cleanup, but not HMAC_CTX_cleanup.
This change checks for both, uses HMAC_CTX_cleanup on platforms which
have it, otherwise falls back to HMAC_cleanup.
This changes makes building GIT on older platforms less tedious.
---
Makefile | 6 ++
configure.ac |
This check will automatically set the correct NO_NSEC setting.
---
configure.ac | 19 +++
1 file changed, 19 insertions(+)
diff --git a/configure.ac b/configure.ac
index 6af9647..3cfdd51 100644
--- a/configure.ac
+++ b/configure.ac
@@ -754,6 +754,25 @@ AC_CHECK_TYPES([struct itime
Jim Hill writes:
> Signed-off-by: Jim Hill
> ---
Please clarify "unwanted" in the proposed commit log message.
It looks to me that the assignment very much deliberate. We know
refnames and 40-hex object names do not contain SP, and the hook is
fed (quoting from Documentation/githooks.txt) lik
Duy Nguyen writes:
> I accidentally created a branch whose name starts with "+".
> Everything went ok until I pushed it because "+" is interpreted as
> forced refspec (e.g. "git push somewhere +wip"). Using full ref names
> would avoid ambiguity. The corner case of this is where the branch
> na
Signed-off-by: Jim Hill
---
templates/hooks--pre-push.sample | 1 -
1 file changed, 1 deletion(-)
diff --git a/templates/hooks--pre-push.sample b/templates/hooks--pre-push.sample
index 69e3c67..6187dbf 100755
--- a/templates/hooks--pre-push.sample
+++ b/templates/hooks--pre-push.sample
@@ -24,7
---
templates/hooks--pre-push.sample | 1 -
1 file changed, 1 deletion(-)
diff --git a/templates/hooks--pre-push.sample b/templates/hooks--pre-push.sample
index 69e3c67..6187dbf 100755
--- a/templates/hooks--pre-push.sample
+++ b/templates/hooks--pre-push.sample
@@ -24,7 +24,6 @@ url="$2"
z40=
Jeff King peff.net> writes:
>
> On Wed, Dec 17, 2014 at 12:53:49PM -0800, Junio C Hamano wrote:
>
> > Michael J Gruber drmicha.warpmail.net> writes:
> >
> > > Rather than extending "git branch" any further[*], I suggest a bolder
> > > strategy:
> > >
> > > - unify/merge for-each-ref and prett
Normally I would use "-D", but send-email (which normally passes options
to format-patch) interprets the "-D" as a case-insensitive abbreviation
for "--dry-run", preventing format-patch from seeing "-D".
Signed-off-by: Eric Wong
---
Case-insensitivity strikes again! :<
What a wacky default for
I accidentally created a branch whose name starts with "+".
Everything went ok until I pushed it because "+" is interpreted as
forced refspec (e.g. "git push somewhere +wip"). Using full ref names
would avoid ambiguity. The corner case of this is where the branch
name is simply "+". Then refspec
28 matches
Mail list logo
