search for: zipper

Justin Bogner <mail at justinbogner.com> writes: > I'll write up some more detailed docs on this, but all you need to do is > a subtree merge to one of the zippered commits. This will then prevent git-biisect from working properly, unfortunately. Maybe most people don't need it be we should be aware of and communicate the tradeoffs. > If you want a monorepo view for all of your branches' histories too it's > more involved, but I'm not...

...lt;joker.eph at gmail.com> writes: > > If you want a monorepo view for all of your branches' histories > > too it's more involved, but I'm not sure anyone really needs > > that. In any case, even if someone does want that the nature of > > the zipper approach means it could be done later > > non-destructively. > > That's true, but then they would suffer the same duplication of > history that motivated you to create the zippered repository in > the first place. > > It isn't clear to me why it...

...out, and start moving forward with the original plan, again... On Mon, Nov 26, 2018 at 2:28 PM James Y Knight <jyknight at google.com> wrote: > It's been a week and a half more (much of which was holiday the US, > granted). If there's no more arguments in favor of going with a zipper > repo, I'd really like to wrap this thread up. > > > On Fri, Nov 16, 2018 at 1:32 AM Justin Bogner <mail at justinbogner.com> > wrote: > >> Yes, I’m still trying to evaluate the migration script’s downsides as >> compared to the zipper approach’s downsides....

Based on the feedback so far, I propose that we call this discussion done -- we will not go with this zippered proposal, but will proceed with https://github.com/llvm-git-prototype/llvm/. On Thu, Nov 15, 2018 at 5:06 PM David Greene via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Tom Stellard via llvm-dev <llvm-dev at lists.llvm.org> writes: > > > What is the status with this...

Yes, I’m still trying to evaluate the migration script’s downsides as compared to the zipper approach’s downsides. Sorry that I got a little held up, but I have to balance evaluating this with getting other work done. I should have some feedback to a few of the responses on this thread next week. I really don’t think I can respond in a useful/productive way before I’ve finished these exp...

Justin Bogner via llvm-dev <llvm-dev at lists.llvm.org> writes: > The layout here is not at all different, only the process by which the > repo is generated. I strongly believe that a history preserving > conversion is very important if we want to avoid making porting > out-of-tree work horribly disruptive. How would an out-of-tree branch be ported with this new approach? Do

...ly not that >> ambitious). >> >> What we should do though in my opinion is go with strict deadlines: i.e. >> every stage of discussion should be open for a very limited time. >> The current linear repo has the edge, but we for example we could leave >> this "zipper" proposal open for the next 1 week (or 2 if you want) as an >> RFC. Unless this alternative gets a high traction then we should close and >> move with the linear history repo. >> >> After almost two years of more or less stagnation, I feel it'd be >> unfortuna...

...e easy > > switchover for existing out of tree forks, or to prioritize having the > best > > conversion we can make. I feel very strongly that the latter should be > the > > priority for the official repository conversion, and that, therefore, we > > should not use the zipper method for the official repository going > forward. > > How do you define "best conversion" here? I may be missing something, > but I really don't see any actual advantage to re-writing the git > history from scratch rather than leveraging the existing git mirrors to &g...

...nk it is a question as to whether to prioritize the easy switchover for existing out of tree forks, or to prioritize having the best conversion we can make. I feel very strongly that the latter should be the priority for the official repository conversion, and that, therefore, we should not use the zipper method for the official repository going forward. However, it's also worth putting much thought into making switchover as easy as possible within the confines of what's possible given that prioritization. On Wed, Oct 31, 2018 at 12:22 PM Justin Bogner via llvm-dev < llvm-dev at lists.l...

In a Readhat 9 system, I have a simple php file "test.php" with the following content to generate Setup.exe: <?php echo exec("pwd"); exec('/usr/bin/wine rar a -a -c- -cfg- -k -m4 -zc:\\\\zipper\\\\Setup.cmt -sfx Setup.exe @c:\\\\zipper\\\\Setup.lst '); ?> When I run it as a CGI script via command line as "php test.php" . The .exe is successfully generated. However, if I load test.php from the browser, the result of "pwd" is shown on the browser but the Setup....

aotheoverlord wrote: > > > Maybe I missed it, but could you tell us which version of PowerBuilder you are using? PowerBuilder 7... I tried to compile the application in PowerBuilder 6, but it doesn't works.

...them into a combined view after each commit. > > While I personally don't see a problem with (1), I've heard people claim > that they want to use the monorepo to bisect arbitrarily far back into > history. If this is the case, we'd prefer an approach like (2). > > A zippered repository gives us a lot of the benefits of the prototype, > without a lot of the issues that are caused by rewriting history: > > - The commits from the official git mirrors exist as they are now, and > we don't need to deal with changing hashes. > > - Out-of-tree bra...

...t;>> >>> While I personally don't see a problem with (1), I've heard people claim >>> that they want to use the monorepo to bisect arbitrarily far back into >>> history. If this is the case, we'd prefer an approach like (2). >>> >>> A zippered repository gives us a lot of the benefits of the prototype, >>> without a lot of the issues that are caused by rewriting history: >>> >>> - The commits from the official git mirrors exist as they are now, and >>> we don't need to deal with changing hashe...

Mehdi AMINI <joker.eph at gmail.com> writes: > Yes, but that's the case for the zipper repo anyway: one merge per > commit. The point is that the second commit is just a trivial merge, > it wouldn't show up in a file `git log` for example. > In the linear rewritten monorepo, adding the history taken from the > existing git mirror would lead to duplicated commits, as i...

...s)) if (nMissing > 0) { idx <- (length(files)+1):N filename <- sapply(as.integer(idx), FUN=sprintf, fmt="file%05d.txt") pathname <- paste(dest, filename, sep="/") for (k in seq(pathname)) cat(file=pathname[k], 0) } # Create a zip archive of the directory zipper <- "C:/cygwin/bin/jar -cfM" cmd <- paste(zipper, " ", dest, ".zip", " ", dest, sep="") system(cmd) # Unse zip.unpack(), which is used by install.packages(), to unpack it. zip.unpack("dir.zip", "c:/tmp") # From Dr. Mingw:...

...kin" <dattier@panix.com> wrote: > Three styles of T-shirts plus hooded sweatshirts, but no FLAC > jackets? seems like slam dunk doesn't it :) but for this run I'm trying to use the same screens on all items to keep the cost down, which rules out the logo on the front of a zippered jacket. still looking for a suitable one where logo can go on the back. if/when I find it I'll add it to the page. Josh ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs

Hi all, I`m a newbie and I need any help!! I want to istall xilinx under win and after the command wine setup.exe Iget the following message: fixme:module:CreateProcessA (D:\ce\jre\1.2\bin\java.exe,...): HIGH_PRIORITY_CLASS ignored fixme:pthread_kill_other_threads_np FIXME:pthread_rwlock_rdlock FIXME:pthread_rwlock_unlock FIXME:pthread_rwlock_rdlock FIXME:pthread_rwlock_unlock

...s)) if (nMissing > 0) { idx <- (length(files)+1):N filename <- sapply(as.integer(idx), FUN=sprintf, fmt="file%05d.txt") pathname <- paste(dest, filename, sep="/") for (k in seq(pathname)) cat(file=pathname[k], 0) } # Create a zip archive of the directory zipper <- "C:/cygwin/bin/jar -cfM" cmd <- paste(zipper, " ", dest, ".zip", " ", dest, sep="") system(cmd) # Unse zip.unpack(), which is used by install.packages(), to unpack it. zip.unpack("dir.zip", "c:/tmp") # From Dr. Mingw:...

...s)) if (nMissing > 0) { idx <- (length(files)+1):N filename <- sapply(as.integer(idx), FUN=sprintf, fmt="file%05d.txt") pathname <- paste(dest, filename, sep="/") for (k in seq(pathname)) cat(file=pathname[k], 0) } # Create a zip archive of the directory zipper <- "C:/cygwin/bin/jar -cfM" cmd <- paste(zipper, " ", dest, ".zip", " ", dest, sep="") system(cmd) # Unse zip.unpack(), which is used by install.packages(), to unpack it. zip.unpack("dir.zip", "c:/tmp") # From Dr. Mingw:...

...erges and stuff > there, makes a pretty nice test case!) > > On Mon, Nov 5, 2018 at 1:07 PM David Greene via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > Mehdi AMINI <joker.eph at gmail.com> writes: > > > Yes, but that's the case for the zipper repo anyway: one merge > per > > commit. The point is that the second commit is just a trivial > merge, > > it wouldn't show up in a file `git log` for example. > > In the linear rewritten monorepo, adding the history taken from > the >...