[EMAIL PROTECTED] writes:
> I still have the patch to make git-http-pull download packs, and I
> should be able to get it to read the objects/info/packs file without
> too much trouble.
Another thing that may help you gain more parallelism in the
initial set of requests is the rev-cache file. Yo
I've been missing for a couple of weeks due to my server dying and needing
to be replaced; I think stuff is mostly back in order now. (But I'm not
yet resubscribed, and I suspect only dumb mailers are currently willing
to talk to my mail server, for some reason I don't yet understand; I'm
sort
Petr Baudis <[EMAIL PROTECTED]> writes:
> Note that I really _loved_ the Daniel's tools while they lasted. What I
> loved most about them was that they really only pulled objects I needed
> and not a single worthless one. Does the current HTTP transport share
> this property?
I am a big fan of Ba
Dear diary, on Sat, Jul 16, 2005 at 07:46:00PM CEST, I got a letter
where Junio C Hamano <[EMAIL PROTECTED]> told me that...
> I do not know what release plan Linus has in mind, and also
> expect things to be quieter next week during OLS and kernel
> summit, but I think we are getting really really
Satturday, 23 July 2005 21:09 Junio C Hamano wrote:
> Instead, please add gitk and gitweb to the list. We should not
> forget that these "mostly read-only" things are Porcelains.
Then add qgit too to provide fair coverage.
--
Respectfully
Alexey Nezhdanov
-
To unsubscribe from this list: send t
Ryan Anderson <[EMAIL PROTECTED]> writes:
> How is this for a start?
A very good start indeed. Thanks.
> Git falls into the category of distributed source code management tools,
> similar to Arch or Darcs (or, in the commercial world, BitKeeper). This
> means that every working directory is a
Ryan Anderson wrote:
Git falls into the category of distributed source code management tools,
similar to Arch or Darcs (or, in the commercial world, BitKeeper). This
means that every working directory is a full-fledged repository with
full revision tracking capabilities.
That's not actually wh
Duplicate send, had typo in orif address line :(
On Saturday 23 July 2005 04:50, Ryan Anderson wrote:
>On Sat, Jul 16, 2005 at 10:46:00AM -0700, Junio C Hamano wrote:
>> - Publicity. I would be very happy to see somebody with good
>>writing and summarizing skills to prepare an article to be
>
On Saturday 23 July 2005 04:15, Ryan Anderson wrote:
>On Sat, Jul 16, 2005 at 10:46:00AM -0700, Junio C Hamano wrote:
>> I do not know what release plan Linus has in mind, and also
>> expect things to be quieter next week during OLS and kernel
>> summit, but I think we are getting really really clo
On Sat, Jul 16, 2005 at 10:46:00AM -0700, Junio C Hamano wrote:
> - Publicity. I would be very happy to see somebody with good
>writing and summarizing skills to prepare an article to be
>published on LWN.NET to coincide with the 1.0 release. An
>update to GIT traffic would also be n
On Sat, Jul 16, 2005 at 10:46:00AM -0700, Junio C Hamano wrote:
> I do not know what release plan Linus has in mind, and also
> expect things to be quieter next week during OLS and kernel
> summit, but I think we are getting really really close.
Looking at the set of patches we just all dumped on
Alexey Nezhdanov <[EMAIL PROTECTED]> writes:
> But this should not be user's problem - it's just the UI that doesn't
> understands when transcoding should be done.
I disagree.
Yes, while you _could_ do something like this to feed text in
local encoding to the VISUAL/EDITOR, and convert it back
Monday, 18 July 2005 09:35 Junio C Hamano wrote:
> Alexey Nezhdanov <[EMAIL PROTECTED]> writes:
> > I'd add the UTF-8 native support. Currently neither commit nor gitk
> > doesn't support that. Probably this should be done at as low as possible
> > level.
>
> I do not understand your proposal. Car
David Lang <[EMAIL PROTECTED]> writes:
> a very common one will be prople who want to setup a cron job to
> update their local tree nightly, in this case having a pre-generated
> pack file with each day's updates will save a significant amount of
> processing power.
>
> would it make sense to have
Alexey Nezhdanov <[EMAIL PROTECTED]> writes:
> I'd add the UTF-8 native support. Currently neither commit nor gitk doesn't
> support that. Probably this should be done at as low as possible level.
I do not understand your proposal. Care to clarify? You can
write your commit messages in UTF-8 t
Satturday, 16 July 2005 21:46 Junio C Hamano wrote:
> I do not know what release plan Linus has in mind, and also
> expect things to be quieter next week during OLS and kernel
> summit, but I think we are getting really really close.
>
> Here are the things I think we would want to see before we hi
On Sat, 16 Jul 2005, Junio C Hamano wrote:
[EMAIL PROTECTED] (Eric W. Biederman) writes:
Junio C Hamano <[EMAIL PROTECTED]> writes:
- Anonymous pull from packed archives on remote sites via
non-rsync, non-ssh transport. ...
... but we may also end up wanting something HTTP
[EMAIL PROTECTED] (Eric W. Biederman) writes:
> Junio C Hamano <[EMAIL PROTECTED]> writes:
>>
>>- Anonymous pull from packed archives on remote sites via
>> non-rsync, non-ssh transport. ...
>> ... but we may also end up wanting something HTTP
>> reachable.
>
> For this we need
Junio C Hamano <[EMAIL PROTECTED]> writes:
> I do not know what release plan Linus has in mind, and also
> expect things to be quieter next week during OLS and kernel
> summit, but I think we are getting really really close.
>
> Here are the things I think we would want to see before we hit
> 1.0:
I do not know what release plan Linus has in mind, and also
expect things to be quieter next week during OLS and kernel
summit, but I think we are getting really really close.
Here are the things I think we would want to see before we hit
1.0:
- Remaining feature enhancements and fixes.
- An
20 matches
Mail list logo
