On Wed, Dec 05, 2012 at 02:30:56AM -0500, Jeff King wrote:
> Anyway, I do think a "shell portability lint" would be a great addition
> to "test-lint", but I am slightly skeptical that it will be easy to
> write a good one that does not have false positives. Still, there may be
> some low-hanging f
On Wed, Dec 05, 2012 at 12:43:30PM +0700, Nguyen Thai Ngoc Duy wrote:
> On Wed, Dec 5, 2012 at 2:39 AM, Junio C Hamano wrote:
> >> Or a project commit hook?
> >
> > Surely. It is OK to have "cd t && make test-lint" in your
> > pre-commit hook.
>
> No, what I meant is a shared pre-commit script
Links of London was established in 1990, the company established by a pair of
background is fish type cuff button order began. A local restaurant for
long-term customers make a pair of silver fish type cuff button as gifts,
design attracted the famous London department store Harvey Nichols, and
ord
Nguyen Thai Ngoc Duy writes:
> On Wed, Dec 5, 2012 at 2:39 AM, Junio C Hamano wrote:
>>> Or a project commit hook?
>>
>> Surely. It is OK to have "cd t && make test-lint" in your
>> pre-commit hook.
>
> No, what I meant is a shared pre-commit script that all git devs are
> encouraged (or forced
Martin von Zweigbergk writes:
> More importantly, when is it desirable not to delete deleted entries?
When I am trying to check out contents of Documentation/ directory
as of an older edition because we made mistakes updating the files
in recent versions, with "git checkout v1.9.0 Documentation/
On Wed, Dec 5, 2012 at 2:39 AM, Junio C Hamano wrote:
>> Or a project commit hook?
>
> Surely. It is OK to have "cd t && make test-lint" in your
> pre-commit hook.
No, what I meant is a shared pre-commit script that all git devs are
encouraged (or forced) to install so bugs are found locally rat
On Sat, Dec 1, 2012 at 1:24 AM, Junio C Hamano wrote:
> Martin von Zweigbergk writes:
>
>> On Thu, Nov 29, 2012 at 2:00 PM, Martin von Zweigbergk
>> wrote:
>>> Slightly off topic, but another difference (or somehow another aspect
>>> of the same difference?) that has tripped me up a few times is
Enable gitk read and write repository specific configuration
file: ".git/k" if the file exists. To make gitk use the local
file simply create one, e.g. with the touch(1) command.
This is very useful if one uses different views for different
repositories. Now there is no need to store all of them i
Enable hiding of tags displayed in the tree as yellow labels.
If a repository is used together with a system like Gerrit
there may be quite a lot of tags used to control building
and there may be hardly any place left for commit subjects.
Signed-off-by: Łukasz Stelmach
---
Rebased onto Paul's rep
Jens Lehmann writes:
> +If you only want to remove the local checkout of a submodule from your
> +work tree without committing that use `git submodule deinit` instead
> +(see linkgit:git-submodule[1]).
I'll add a comma between "without commiting that" and "use X
instead"; it will read better, I
With "git submodule init" the user is able to tell git he cares about one
or more submodules and wants to have it populated on the next call to "git
submodule update". But currently there is no easy way he could tell git he
does not care about a submodule anymore and wants to get rid of his local
w
Torsten Bögershausen writes:
> On some systems sed allows the usage of e.g.
> sed -i -e "s/line1/line2/" afile
> to edit the file "in place".
> Other systems don't allow that: one observed behaviour is that
> sed -i -e "s/line1/line2/" afile
> creates a backup file called afile-e, which breaks th
Hi guys,
I tried to use url.insteadof to get URLs mapped correctly, starting with a
double-slash (//). Unfortunately, Git doesn't recognize that and still tries to
connect to the original URL. I am using Git in a productive environment. On
Windows desktops, MsysGit 1.7.11 and 1.8.0. On ubuntu
W dniu 03.12.2012 22:15, Stefan Haller pisze:
> Lukasz Stelmach wrote:
>
>> Enable gitk read and write repository specific configuration
>> file: ".git/k" if the file exists. To make gitk use the local
>> file simply create one, e.g. with the touch(1) command.
>
> I'm not sure I like this propos
On some systems sed allows the usage of e.g.
sed -i -e "s/line1/line2/" afile
to edit the file "in place".
Other systems don't allow that: one observed behaviour is that
sed -i -e "s/line1/line2/" afile
creates a backup file called afile-e, which breaks the test.
As sed -i is not part of POSIX, avo
Nguyen Thai Ngoc Duy writes:
>> This (once it gets cleaned up to reduce false positives) belongs to
>> "cd t && make test-lint".
>
> Or a project commit hook?
Surely. It is OK to have "cd t && make test-lint" in your
pre-commit hook.
A few more things in addition to what Torsten's script attem
On Tue, Dec 4, 2012 at 6:12 PM, Johannes Schindelin
wrote:
> Hi kusma,
>
> On Sat, 1 Dec 2012, Erik Faye-Lund wrote:
>
>> On Fri, Nov 30, 2012 at 6:58 PM, Johannes Schindelin
>> wrote:
>> > Hi,
>> >
>> > On Tue, 13 Nov 2012, Erik Faye-Lund wrote:
>> >
>> >> Set a control-handler to prevent the pr
Hi kusma,
On Sat, 1 Dec 2012, Erik Faye-Lund wrote:
> On Fri, Nov 30, 2012 at 6:59 PM, Johannes Schindelin
> wrote:
> > Hi,
> >
> > On Tue, 13 Nov 2012, Erik Faye-Lund wrote:
> >
> >> By moving the echo-disabling code to a separate function, we can
> >> implement OS-specific versions of it for n
Hi kusma,
On Sat, 1 Dec 2012, Erik Faye-Lund wrote:
> On Fri, Nov 30, 2012 at 6:58 PM, Johannes Schindelin
> wrote:
> > Hi,
> >
> > On Tue, 13 Nov 2012, Erik Faye-Lund wrote:
> >
> >> Set a control-handler to prevent the process from terminating, and
> >> simulate SIGINT so it can be handled by
Hi kusma,
On Tue, 4 Dec 2012, Erik Faye-Lund wrote:
> in ab1a11be ("mingw_rmdir: set errno=ENOTEMPTY when appropriate"),
> a check was added to prevent us from retrying to delete a directory
> that is both in use and non-empty.
>
> However, this logic was slightly flawed; since we didn't return
On Sat, Nov 24, 2012 at 9:44 PM, Eric S. Raymond wrote:
> git presently contains one Python extension command, Pete Wycoff's p4
> importer. If my git-weave code is merged it will acquire another.
Write a really compelling tool. Don't argue languages. Make it
wonderful. The git maintainers, tool
- Original Message -
> From: "Felipe Contreras"
> Sent: Tuesday, December 4, 2012 9:19:18 AM
> Subject: Re: Python extension commands in git - request for policy change
>
> > > Also, you are ignoring all the advantages that shell has and
> > > python does not.
> >
> > Out of curiosity, ca
On Mon, Dec 3, 2012 at 3:45 PM, Philippe Vaucher
wrote:
>> Also, you are ignoring all the advantages that shell has and python does not.
>
> Out of curiosity, can you list the advantages? From what I gathered:
>
> - no need to install bash
Unless you are in Windows or OS X. OS X has a shell, but
While not being a huge problem, you may or may not want to correct one
commit message:
* aaf5ad5 (origin/next, gitster/next) Sync with 1.8.0-rc0
|\
| * ee26a6e (tag: v1.8.1-rc0, origin/master, origin/HEAD,
gitster/master) Git 1.8.1-rc0
Cheers,
Michael
--
To unsubscribe from this list: send the
Junio C Hamano wrote:
> I've sent comments on small nits I found but overall they looked
> quite well researched. Will tentatively queue on the 'pu' branch,
> expecting further updates and Acks from people involved polishing
> these patches.
>
> Thanks for writing it up.
Thanks all. I think th
in ab1a11be ("mingw_rmdir: set errno=ENOTEMPTY when appropriate"),
a check was added to prevent us from retrying to delete a directory
that is both in use and non-empty.
However, this logic was slightly flawed; since we didn't return
immediately, we end up falling out of the retry-loop, but right
On 11/30/2012 08:50 PM, Torsten Bögershausen wrote:
>> Having a ".git" entry inside a tree can cause confusing
>> results on checkout. At the top-level, you could not
>> checkout such a tree, as it would complain about overwriting
>> the real ".git" directory. In a subdirectory, you might
>> check
Junio C Hamano writes:
> So let's do a lot simpler patch instead.
>
> -- >8 --
> From: Jeff King
> Date: Mon, 3 Dec 2012 01:16:57 -0500
>
> If the user has unset advice.statusHints, we already
> suppress the "use git reset to..." hints in each stanza. The
> new "use git push to publish..." hint
There's no remaining call-sites, and as pointed out in the
previous commit message, it's not quite ideal. So let's just
lose it.
Signed-off-by: Erik Faye-Lund
---
compat/mingw.c | 15 ---
compat/mingw.h | 2 --
2 files changed, 17 deletions(-)
diff --git a/compat/mingw.c b/compat/m
The getpass-implementation we use on Windows isn't at all ideal;
it works in raw-mode (as opposed to cooked mode), and as a result
does not deal correcly with deletion, arrow-keys etc.
Instead, use cooked mode to read a line at the time, allowing the
C run-time to process the input properly.
Sinc
On Windows, the terminal cannot be opened in read-write mode, so
we need distinct pairs for reading and writing. Since this works
fine on other platforms as well, always open them in pairs.
Signed-off-by: Erik Faye-Lund
---
compat/terminal.c | 29 ++---
1 file changed, 18
By moving the echo-disabling code to a separate function, we can
implement OS-specific versions of it for non-POSIX platforms.
Signed-off-by: Erik Faye-Lund
---
compat/terminal.c | 43 +--
1 file changed, 25 insertions(+), 18 deletions(-)
diff --git a/com
Set a control-handler to prevent the process from terminating, and
simulate SIGINT so it can be handled by a signal-handler as usual.
Signed-off-by: Erik Faye-Lund
---
compat/mingw.c | 76 ++
compat/mingw.h | 6 +
2 files changed, 72 i
Make sure SIG_DFL for SIGALRM exits with 128 + SIGALRM so other
processes can diagnose why it exits.
While we're at it, make sure we only write to stderr if it's a
terminal, and change the output to match that of Linux.
Signed-off-by: Erik Faye-Lund
---
compat/mingw.c | 7 +--
1 file chang
So here's v2 of this series. For reference, you can find v1 and
it's discussions here:
http://mid.gmane.org/1352815288-3996-1-git-send-email-kusmab...@gmail.com
The changes since the last round:
* 1/6: This patch has been added. It was missing in the last round,
due to stupidity on my b
35 matches
Mail list logo