On Wed, Dec 25, 2013 at 5:28 PM, Wolfgang Rohdewald
wrote:
> Am Mittwoch, 25. Dezember 2013, 17:14:31 schrieb Drew Northup:
>> Git does not use KDE's language packs.
>
> Sorry, I meant ubuntu. I believe I heard before that they tend to replace
> upstream translatio
would be worth considering if
your questions are Git questions or web-app design questions. The
latter should be taken elsewhere.)
--
-Drew Northup
--
"As opposed to vegetable or mineral error?"
-John Pescatore, SANS NewsBites
%3a13.10+20131012_all.deb
What does dpkg report for info about the installed git package (if you
are using the packaged version)?
--
-Drew Northup
--
"As opposed to vegetable or mineral error?"
-John Pescatore, SANS NewsBites Vol
for dealing
with some of the advanced usage explanations it can be argued that the
"staging area" metaphor (it implies _completed_ bundles ready to
package into commits and ship--I envision shipping trailers being
filled with _immutable_ boxes and attached to truck
On Thu, Aug 29, 2013 at 6:10 PM, Felipe Contreras
wrote:
> On Thu, Aug 29, 2013 at 4:55 PM, Drew Northup wrote:
>> On Thu, Aug 29, 2013 at 2:37 PM, Junio C Hamano wrote:
>>> Felipe Contreras writes:
>>>
>>>> It has been discussed many times in the past
On Fri, Aug 30, 2013 at 1:16 AM, Piotr Krukowiecki
wrote:
> Drew Northup napisał:
>>I agree with Junio. This effort is better spent making the
>>documentation clearer and more succinct. The reality is that a user
>>needs to build a model in their mind of what they are doin
the object store with the content and tree objects. Sometimes we
create tag objects to record something special about commits, trees,
and content blobs.
That's the real model (with some rough edges). Explaining what that
has to do with distributed version control is the hard part.
--
-Drew Nort
g log --no-color --pretty=raw --parents --parents --
fatal: bad revision 'log'
This fix works by properly and fully initializing "buf" before each use.
github issue # 167
Helped-by: Jonas Fonseca
Signed-off-by: Drew Northup
---
This should apply cleanly to the tig public master
On 07/19/2013 12:07 AM, Jonas Fonseca wrote:
On Thu, Jul 18, 2013 at 9:30 AM, Drew Northup wrote:
Somehow this patch breaks the main view to not open the correct commit in diff view
when is pressed. Back to the debugger...
Does this (possibly white-space damaged) patch work for you?
It
On Fri, Jul 19, 2013 at 12:07 AM, Jonas Fonseca wrote:
> On Thu, Jul 18, 2013 at 9:30 AM, Drew Northup wrote:
>>
>> Somehow this patch breaks the main view to not open the correct commit in
>> diff view when is pressed. Back to the debugger...
>
> Does this (possibly
Somehow this patch breaks the main view to not open the correct commit
in diff view when is pressed. Back to the debugger...
On 07/18/2013 12:51 AM, Drew Northup wrote:
Since c7d67ab running "tig" with no options has failed with the
error "tig: No revisions match the given a
if (fd>= 0)
return fd;
/*
* Fatal error (EPERM, ENOSPC etc).
--
-Drew Northup
--
"As opposed to vegetable or mineral error?"
-John Pescatore, SANS NewsB
license.
On 07/09/2013 11:33 AM, Drew Northup wrote:
The function mkstemps() isn't available in all libc implementations. In
glibc it first became available in 2.11, so platforms such as RHEL 5&
Slackware 13 lack it. This is likely true of many non-LINUX platforms
as well.
This fixes brea
g log --no-color --pretty=raw --parents --parents --
fatal: bad revision 'log'
This fix works by teaching tig that when it is supplied with a
blank field in the source argument buffer that it should skip
over that field and continue instead of copying the previous
field value into the destinati
eate temporary
file with name as suffix."
Signed-off-by: Drew Northup
---
This work-around is taken from Git and was inspired by code in libiberty.
It is presumed that this isn't a problem due to compatible license terms.
A (virtually identical) version of this available in
https://g
ody who is interested in
> tying its loose ends.
I'd like to have a closer look at these. It may be a week however as
there's some serious in-house chaos going on right now. (Finally
starting to settle after about 2 months...)
--
-Drew Northup
-
)
as noted in the documentation. Yes, it's a small change, but let
Junio decide what to just squash in. It is much faster for him to just
pull in the commit than to find what you've noted by hand and fix it
in most cases.
--
-Drew Northup
--
On Tue, Apr 16, 2013 at 6:26 PM, Jonathan Nieder wrote:
> Drew Northup wrote:
>
>> This is unobtrusive yet to the point.
>
> I agree with the spirit.
>
> [...]
>> --- a/Documentation/gitweb.conf.txt
>> +++ b/Documentation/gitweb.con
Forgot the S-O-B...
On Tue, Apr 16, 2013 at 8:47 AM, Drew Northup wrote:
> On Tue, Apr 16, 2013 at 8:26 AM, Jakub Narębski wrote:
>
>> Drew: gitweb(1) or gitweb.conf(5) solution is more involved, so
>> perhaps something like that?
>
>
> That or: (or both I suppose..
.
Locations of the common system-wide configuration file, the fallback
system-wide configuration file and the per-instance configuration file
--
1.8.0
--
-Drew Northup
--
"As opposed to vegetable or mineral error?"
-John Pes
On Tue, Apr 16, 2013 at 12:36 AM, Junio C Hamano wrote:
> Drew Northup writes:
>
>>> + Note that the GITWEB_CONFIG_SYSTEM system-wide configuration file is
>>> + only used for instances that lack per-instance configuration file.
>>> + You can use GITWEB
rical behavior (and backward compatibility)
> has place (if any) in manpages, not gitweb/INSTALL.
> --
> Jakub Narębski
Let us then agree that it should be mentioned somewhere in
gitweb.conf.txt then (as it currently is not).
--
-Drew Northup
-
ext is easier on the eyes it fails to note why we
don't just dump our idiosyncratic way of doing things and just make
the system-wide defaults act individually. This information is useful
to system administrators, as it explains what is act
t; part of
the explanation entirely we can expect to end up in exactly the
situation that I complained about to begin with. (Or we could just do
this the way everybody else does, with partial overrides being the
common case, starting at 2.x and no longer hav
ll give a clear signal of the
prominence of those segments of code versus others elsewhere in the
"git stat" flow path. That information will tell us more clearly what,
if anything, it is worth keeping a cache of and what form that cache
should take.
--
-Drew Northup
--
sing is (something written in python if I'm not
mistaken), but @$dayjob we've managed to authenticate to Google Apps
using SAML 1.1 & SAML2 wrappers "living" in both CAS and Shibboleth.
SAML is a standard and is supported (in whole or in part) by a lot of
syst
the description ofthe receive.denyCurrentBranch option
> +in linkgit:git-config[1] for details.
This looks safe to me, with the minor nit that "ofthe" ("of the")
isn't one word.
--
-Drew Northup
--
"As o
2011 +
Autogenerated HTML docs for v1.7.7-rc0-72-g4b5ea
n1xim@atom:~/tmp/git_dev/git$ git log refs/remotes/origin/man
commit e193e4189407968b3c46992e3eac60d38424286e
Author: Junio C Hamano
Date: Wed Aug 31 00:49:25 2011 +
Autogenerated manpages for v1.7.7-rc0-72-g4b5ea
I
depends largely upon the
filesystem and VFS api in use. It is not unheard of that a delete
operation actually consist of moving the reference to the item's own
allocation marker into a "trashcan" to be cleaned up after later.
In other words, I'
4) that requires the most user interaction. I could see
building up a shell script that does all but (4) nearly automatically.
None of this requires modifying Git itself.
--
-Drew Northup
--
"As opposed to vegetable or mineral error?&q
;s solution doesn't suffer from this recursivity problem.
--
-Drew Northup
--
"As opposed to vegetable or mineral error?"
-John Pescatore, SANS NewsBites Vol. 12 Num. 59
--
To unsubscribe from this list: send the line &quo
ths_ was acceptable (which isn't a
pathspec, as it isn't a search expression) and other places where
_only_ a single path was acceptable. Should that fail to be the case
then there would be a good argument for changing the affected
instances of "" to "" in the documentat
ory, but it's not automated).
>
> can we introduce a new or extend existing transports to support that ?
How would the broken repository be sure of what it is missing to
request it from the other side?
--
-Drew Northup
--
"As
see this being an improvement for enough users to
justify the extra noise.
Granted, I am not the definitive word on much of anything around here,
but I cannot see this making much sense in the big picture of things.
If you wanted to make this change to something more like Googl
exercise left to the
reviewer to find that you're talking about this thread:
http://thread.gmane.org/gmane.comp.version-control.git/208354
Cheers.
--
-Drew Northup
--
"As opposed to vegetable or mineral error?"
-John Pesca
On Mon, Nov 12, 2012 at 3:24 PM, Jeff King wrote:
> On Mon, Nov 12, 2012 at 01:55:46PM -0500, Drew Northup wrote:
>
>> On Sun, Nov 11, 2012 at 6:28 PM, glpk xypron wrote:
>> > Gitweb can be used to generate an RSS feed.
>> >
>> > Arbitrary tags can be in
an idea. Interesting, or terrible? :)
Done at least once already:
http://comments.gmane.org/gmane.comp.version-control.git/201591
--
-Drew Northup
--
"As opposed to vegetable or mineral error?"
-John Pescatore, SANS News
ion.
>
> Care to explain?
If I have an email thread I'd like to store alongside a commit I'll
put that into a note, but I usually don't push that kind of thing out
to a remote repo.
Does that help?
--
-Drew Northup
---
ted to reconstruct CC list of discussion]
--
-Drew Northup
--
"As opposed to vegetable or mineral error?"
-John Pescatore, SANS NewsBites Vol. 12 Num. 59
--
To unsubscribe from this list: send the line "unsubscribe git"
On Mon, Oct 29, 2012 at 7:35 AM, Jeff King wrote:
> On Mon, Oct 29, 2012 at 07:21:52AM -0400, Drew Northup wrote:
>> > I would have expected git to at least complain about updating an
>> > annotated tag with another annotated tag. But it actually uses the same
>> >
d a patch set
including the snippet that Kacper posted earlier (1) in response to my
comment about not being sure how complicated all of this would be or
not?
[1] http://article.gmane.org/gmane.comp.version-control.git/208473
--
-Drew Northup
here's somebody better
than me to take this over I'd be game for that too...)
--
-Drew Northup
--
"As opposed to vegetable or mineral error?"
-John Pescatore, SANS NewsBites Vol. 12 Num. 59
--
To unsubscrib
27;s patch, some manpage changes, a test.
Angelo, may we use your original mail as the source for the cover page?
--
-Drew Northup
--
"As opposed to vegetable or mineral error?"
-John Pescatore, SANS NewsBites Vol. 12 Num.
On Fri, Oct 26, 2012 at 1:42 PM, Kacper Kornet wrote:
> On Thu, Oct 25, 2012 at 05:16:00PM -0400, Drew Northup wrote:
>> On Thu, Oct 25, 2012 at 3:05 PM, Angelo Borsotti
>> wrote:
>> > Are remote repositories less protected than the local ones? I
>> > thin
On Fri, Oct 26, 2012 at 9:59 AM, Chris Rorvick wrote:
> On Fri, Oct 26, 2012 at 8:37 AM, Drew Northup wrote:
>> (As for deleting the current branch, you can't really do that on a
>> proper bare remote anyway as there is no such thing as a "current
>> branch" i
On Fri, Oct 26, 2012 at 2:42 AM, Angelo Borsotti
wrote:
> Hi Drew,
>
--Adding for clarity: On Thurs, Oct 25, 2012 at 17:16 EDT, Drew
Northup wrote:
>>
>> Changing the tag in the local repository is a tag modification
>> operation. Pushing that change to a remote rep
On Thu, Oct 25, 2012 at 3:05 PM, Angelo Borsotti
wrote:
---At 13:19 on Oct 25, 2012, Drew Northup wrote: [added for clarity]
>>Tags have many uses. Some of those uses are harmed when tags change
> and some aren't. That's a philosophical argument
>
> I agree, but in this c
es are harmed when tags change
and some aren't. That's a philosophical argument and Git is a computer
program, not a philosopher. It is not the job of the machine to
prevent the user from shooting himself in the foot when he clearly
expressed an interest in doing so.
--
-Drew Northup
---
and ~/.git-prompt.sh.
>
> Proposal:
>
> 1) /usr/lib/git-core/git-sh-prompt
> 2) git-sh-prompt(1)
>
> Sensible?
Does the LSB provide any guidance? If not, or if such guidance isn't
helpful, I say that looks reasonable.
What I'd like to know is why we are saying &
them as zip
archives and diff what's inside of them. The text in particular is
stored as XML.
--
-Drew Northup
--
"As opposed to vegetable or mineral error?"
-John Pescatore, SANS NewsBites Vol. 12 Num. 59
--
To unsubscribe fr
etch $from $branch:" to
> explicitly decline copying.
How are we supposed to remember those are different?
"git fetch $from $branch..."
VS
"git fetch $from $branch:"
I strongly prefer EXPLICITLY setting tracking than
On Sat, Oct 20, 2012 at 10:34 PM, wrote:
> On Sat, 20 Oct 2012, Drew Northup wrote:
>> On Sun, Oct 14, 2012 at 12:57 AM, wrote:
>>> On Sat, 13 Oct 2012, Junio C Hamano wrote:
>>>> da...@lang.hm writes:
>>>>>
>>>>> today I h
7;what is', the result of changes from all the tools.
>
> The systems are all built with a standard image, but the automation tools I
> do have tend to push identical files out to many of the systems (or files
> identical except for a couple of lines)
David,
Is there any particular
On Wed, 2012-10-10 at 14:47 -0700, Junio C Hamano wrote:
> Drew Northup writes:
>
> > # Untracked files:
> > # (use "git add ..." to include in what will be committed)
> > #
> > # rc.d/rc2.d/S08iptables
> > # rc.d/rc3.d/S08iptables
>
undergoing testing.
>
> Thanks,
>
> Jim Vahl
Jim,
Have you looked at http://git-scm.com/book yet? It sounds to me like you
have some misconceptions about how Git works. (If so, did it leave you
more or less confused?)
--
-Drew Northup
I use etckeeper on some of my systems, backed by Git. On a system still
using a SYSV style init I recently modified my iptables settings,
changing which runlevels would stop/start the firewall.
[root@drew-northup ~]# etckeeper vcs status
# On branch master
# Changes not staged for commit
of these commands (in your case, gitk) knows that any change in the
>> information returned by lstat(2) on the paths in the working tree
>> files since that call indicate real changes to the files.
>>
>> "git status" internally runs an equivalent of "--refresh&
alanced setup
then applying TCP/IP like back-off semantics is the right way to go.
The only reason the network stack isn't doing it for you is because
the load balancers wait for the SSL/TLS start before dumping the
"excess" (exceeding of license) SSL connections.
--
-Drew Northup
-
refore, I would not attempt to argue that the results that apply to
their systems would apply much of anywhere else. (They have done
presentations publicly, which are archived on the 'net, about how they
do things.)
--
-Drew Northup
--
e. "DWIM" is a very fraught concept because you are assuming that
everybody is going to want to do things exactly (or nearly so) the way
you do.
>> I think that this is a road to insanity; anybody who thinks along
>> this line is already on the other side of the line, I would
Make note that while the --follow option is accepted by git blame it does
nothing.
Signed-off-by: Drew Northup
---
Documentation/git-blame.txt | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/Documentation/git-blame.txt b/Documentation/git-blame.txt
index 7ee9236..7465bd8
rectly?
> Example screenshot:
> http://i.imgur.com/06skV.png
Joseph,
What character set is that supposed to be in? In addition, if it is
UTF-(something), what code segment are you using?
--
-Drew Northup
--
"As opposed to vegetable
ly disabled in this case.
(Given that you seem to be working on a Mac I suspect that "disabled" is
likely the default setting for that configuration item.)
--
-Drew Northup
"As opposed to vegetable or mineral error?"
-John Pes
think of off hand is that the
documentation is describing what the program options do to the user (a
different "audience")--which explains why the text wasn't in
imperative form to begin with.
--
-Drew Northup
--
&quo
Can you tell me about this or reference a site or page that
> discusses it?
Jean,
If you take a close look at the git.git repo itself you will notice that
several different (and at times totally non-overlapping) branches are
available. The same option is available for other projects as
SH or file share?
>
> Can someone help me with this?
Raj,
You may find that using Gitolite [1] (and following the documentation
that comes with it) to be a good solution to what you are trying to
do.
(1): https://github.com/sitaramc/gitolite/
--
-Drew Northup
--
rior the divergence
and pull the changes onto the production system--re-applying those
changes you discovered in the "git diff -b -w" step on a developer's
system first, in a temporary branch, before doing the reset, merging
back to development, etc.
So, in conclusion, this is a sit
ults). (I am writing this from the
webmail interface in the hopes that it goes through.)
Am I the ONLY ONE seeing this?
--
-Drew Northup
--
"As opposed to vegetable or mineral error?"
-John Pescatore, SANS NewsBites Vol. 12 Num.
o things outside of the base
Document Root all sorts of interesting possibilities for failure
become available.
I am pretty sure that this isn't a Git problem, it is a CGI hosting /
configuration problem. An Apache-centric list may be able to help you
be
ying tens of thousands
of them. Most of us can't afford that. (Yes, there is an overhead to
building packages. I've done it enough times to know about that quite
intimately.)
Packages and package management are great for system softwar
e use of the
community's time? So many platforms include standard varieties of MAKE
and it is well supported by the autotools framework. Tons of people
know how to maintain it.
So it may sound cool, but that alone does not make it a good idea.
g I was trapped in a DOS prompt was bad.
Dreaming in patches? OUCH!
--
-Drew Northup
--
"As opposed to vegetable or mineral error?"
-John Pescatore, SANS NewsBites Vol. 12 Num. 59
--
To unsubscribe from this list: send the line
72 matches
Mail list logo
