git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [QUESTION] Selective fetch possible?

From
FZFilippo Zangheri <filippo.zangheri@yahoo.it>
Date
Mar 11, 2008, 12:29 UTC
Message-ID
<47D67B16.8040709@yahoo.it>
In-Reply-To
<47D64BE4.9010009@dawes.za.net>

Rogan Dawes ha scritto: (...)

Show 11 quoted lines
> I think that one should not *expect* to be able to complete merges with 
> only a partial checkout, though. It *may* work in cases where there are 
> no conflicts, but I think it would be a perfectly valid error path to 
> fail if there is a conflicting merge in a part of the tree that has not 
> been checked out.
> 
> So, for a user working on partial trees, they would be able to modify 
> their partial tree, and check in their changes, but merges would have to 
> be done by someone with a complete checkout. For the given examples 
> where partial trees make sense (documentation workers), this seems like 
> a reasonable compromise.

I think this is what every reasonable developer should have in mind when he's working on just a project subset :). And I also think, this is not a valid reason for forbidding/not implementing such a partial (or subtree) checkout.

-- 
Filippo Zangheri

GPG key ID: 0xE1D879FA
Key fingerprint: 816B CE57 D43C 0A47 EF35 3378 EA5F A72A E1D8 79FA
Key server: pgp.mit.edu

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GE d- s+:- a-- C++ UL+++ P+ L+++ E-- W+ N* o-- K- w--- O-- M--
V- PS++ PE+ Y+ PGP++ t 5-- X++ R* tv b+ DI-- D---- G-- e++ h--
r++ z*
------END GEEK CODE BLOCK------
Previous: Rogan Dawes
Message 7 of 7 in “[QUESTION] Selective fetch possible?”
  1. Filippo ZangheriMar 10, 2008
  2. Shawn O. PearceMar 10, 2008
  3. Jakub NarebskiMar 10, 2008
  4. Rogan DawesMar 11, 2008
  5. Shawn O. PearceMar 11, 2008
  6. Rogan DawesMar 11, 2008
  7. Filippo ZangheriMar 11, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.