Search type Search syntax
Tags [tag]
Exact "words here"
Author user:1234
user:me (yours)
Score score:3 (3+)
score:0 (none)
Answers answers:3 (3+)
answers:0 (none)
isaccepted:yes
hasaccepted:no
inquestion:1234
Views views:250
Sections title:apples
body:"apples oranges"
URL url:"*.example.com"
Favorites infavorites:mine
infavorites:1234
Status closed:yes
duplicate:no
migrated:no
wiki:no
Types is:question
is:answer
Exclude -[tag]
-apples
For more details on advanced search visit our help page
Results tagged with Search options answers only user 1352

Git is an open-source DVCS (Distributed Version Control System)

9
votes
Gitk is built on top of a GUI library named "Tk", a graphical toolkit originally designed for the Tcl language. "Gitk" is a combination of "Git" + "Tk" and then they removed the extra "t" in the middle. Thus, "k" literally stands for "kit". …
answered Oct 9 '15 by Jörg W Mittag
0
votes
This cannot possibly work. Git cannot clone any files that it doesn't even know exist. That doesn't even have anything to do with Git, that's just basic common sense. …
answered Mar 9 '13 by Jörg W Mittag
63
votes
the category of endofunctors" The Git thing, however, is just random gibberish. It is meant to resemble the monad joke, and might also be a jab at the darcs patch theory, but fundamentally, the … person making the joke didn't understand the monad joke. Sources: This is the original tweet containing the quote: Wil Shipley (‏@wilshipley): Sweet god I hate git. Isaac Wolkerstorfer …
answered Sep 16 '14 by Jörg W Mittag
2
votes
addresses: send a letter with an unforgeable token via verified mail, then verify that the claimant knows the token. So, for a Git repository, you could tell the claimant to put a blob with certain content … just need to make sure not to run the garbage collector before the verification process is over, otherwise the object will be collected. Of course, not everybody knows how to put a blob into a Git
answered Dec 2 '18 by Jörg W Mittag
7
votes
programming languages: one concept == one line. If minor changes occur, the file change should be minor as well. Git logically always stores a snapshot of the entire file per revision … , regardless of whether the file is binary or text. (In fact, Git doesn't care about the contents of files at all, so the very concept of "text" or "binary" is fundamentally meaningless.) The physical storage …
answered May 6 '17 by Jörg W Mittag
7
votes
There are two problems to consider: How do you review such a commit? How do you attribute it? It is clear that the commit will be so massive that it is practically impossible to review. What you s …
answered Apr 10 by Jörg W Mittag
1
vote
versions are lost. Unfortunately, it is now too late for that, unless you want to rewrite the entire history of the Git repository. I only mention it for the benefit of readers who come to this … question at an earlier point. However, you can still do the same thing in a separate repository and use the "graft" feature of Git to graft this repository's history onto your real one. This is for …
answered Mar 1 by Jörg W Mittag
6
votes
This really has nothing to do with Git. It's a bad idea in general to edit a live website while your users are using it. You should make sure that your edits are complete, then "go live". …
answered Feb 4 '13 by Jörg W Mittag
1
vote
Git distinguishes between authoring a change (actually writing the code in the change) and committing a change (adding the change to the repository), and tracks both the author and committer, as well … patch authored before the parent commit was committed. Git shows the author data by default (and fills in the values from the commit data if missing). In addition, Git allows you to override the …
answered Apr 5 '16 by Jörg W Mittag
15
votes
It is true that Git stores only full revisions of entire files. However, it does not simply store them in the file system as individual files. Instead, it stores them in a pack file. A pack file is … even compress identical blocks of content in unrelated files, such as GPL license headers (which is something patch-based storage formats cannot do with the same ease). In general, a Git repository will end up smaller than a Subversion repository, even though the latter only stores patches. …
answered Sep 19 '12 by Jörg W Mittag
11
votes
Git doesn't care about the contents of files. At all. It stores a directory tree*. That's it. It stores the names of directories and files, and their contents but without ever looking at the content … changes between different branches; these higher-level tools obviously do need to know about the contents of files. Git itself ships with some tools that can effectively and efficiently do that with …
answered Nov 18 '16 by Jörg W Mittag
6
votes
-day period when Linus wrote Git, i.e. even before he published the code. I think there was one backwards-incompatible change in one of the remote protocols many many years ago. However, in that case …
answered Jul 10 '13 by Jörg W Mittag
8
votes
GitHub is proprietary and is hosted on GitHub.
answered Oct 3 '12 by Jörg W Mittag
1
vote
There are some filesystems and/or filesystem implementations and/or libc implementations where performance degrades with large numbers of directory entries.
answered Nov 1 '15 by Jörg W Mittag
36
votes
I'd go with option 4: explain to the contributor why his pull request doesn't fit the project's goals (and in the process give the contributor a chance to explain why he thinks it does) and ask him to …
answered Oct 10 '13 by Jörg W Mittag

15 30 50 per page